...
[16:08:02 CDT(-0500)] <EricDalquist> not sure, I'd have to look or ask nick
[16:09:04 CDT(-0500)] <athena> if he's around at some point this week it might be good to catch up on that stuff
[16:48:44 CDT(-0500)] <athena> in the meantime sending an email summarizing what i think i'm seeing
[16:48:51 CDT(-0500)] <athena> what's our status on being able to do HTML5?
[16:48:55 CDT(-0500)] <EricDalquist> sounds good
[16:48:56 CDT(-0500)] <EricDalquist> never
[16:49:05 CDT(-0500)] <athena> so . . . uhhhh
[16:49:10 CDT(-0500)] <athena> we may actually need to figure that out
[16:49:13 CDT(-0500)] <EricDalquist> realistically portlets will never let us do html5
[16:49:24 CDT(-0500)] <EricDalquist> unless EVERY html5 portlet renders valid html5
[16:49:30 CDT(-0500)] <EricDalquist> the whole page will fail to render
[16:49:33 CDT(-0500)] <athena> yeah, i remember talking about this some before
[16:49:40 CDT(-0500)] <EricDalquist> so ... yeah
[16:49:43 CDT(-0500)] <athena> so why does it fail if one doesn't due HTML5?
[16:50:00 CDT(-0500)] <EricDalquist> because html5 requires structurally valid XML if I remember correctly
[16:50:06 CDT(-0500)] <EricDalquist> so if one portlet screws that up
[16:50:11 CDT(-0500)] <EricDalquist> the browser barfs
[16:50:22 CDT(-0500)] <athena> does it have to be valid HTML5 or just valid XML?
[16:50:34 CDT(-0500)] <EricDalquist> I'm not sure
[16:50:47 CDT(-0500)] <athena> can't we just ship with portlets that work?
[16:51:06 CDT(-0500)] <EricDalquist> essentially our best bet would be to really dig into the portlet APIs support for portal<->portlet content type communication
[16:51:26 CDT(-0500)] <EricDalquist> and go through and make all our jasig portlets correctly declare that they support the html5 content type
[16:51:40 CDT(-0500)] <EricDalquist> and then the portal can render a html5 theme if every portlet on the page declares support for it
[16:51:50 CDT(-0500)] <EricDalquist> and if not we have to fall back to something other than html5
[16:51:57 CDT(-0500)] <EricDalquist> though I think you could still render the html5 theme
[16:52:04 CDT(-0500)] <EricDalquist> and just set content type to something like text/html
[16:52:07 CDT(-0500)] <EricDalquist> its really gross
[16:52:19 CDT(-0500)] <EricDalquist> and a fairly significant amount of work
[16:52:24 CDT(-0500)] <athena> i think we are going to need to start supporting html5, particularly for mobile
[16:52:29 CDT(-0500)] <athena> so perhaps umobile can help out with it
[16:52:34 CDT(-0500)] <EricDalquist> yeah
[16:52:40 CDT(-0500)] <EricDalquist> well umobile will be easier
[16:52:45 CDT(-0500)] <athena> so what does every single portlet need to support HTML5?
[16:52:47 CDT(-0500)] <EricDalquist> sicne you only ever have 1 portlet at a time on a page
[16:52:58 CDT(-0500)] <EricDalquist> every portlet rendered on the page needs to support it
[16:53:07 CDT(-0500)] <EricDalquist> or it could render output that isn't valid
[16:53:11 CDT(-0500)] <EricDalquist> and make the browser barf
[16:53:34 CDT(-0500)] <athena> that's only true if there's content that's valid HTML4 that's not valid in HTML5, right?
[16:53:56 CDT(-0500)] <EricDalquist> or if there is structurally invalid content I believe
[16:54:24 CDT(-0500)] <athena> does look like there's a distinction between HTML5 and XHTML5
[16:54:37 CDT(-0500)] <athena> perhaps we'd be in better shape w/ the non-XHTML version?
[16:54:40 CDT(-0500)] <EricDalquist> yeah
[16:54:45 CDT(-0500)] <EricDalquist> its worth a try
[16:54:52 CDT(-0500)] <EricDalquist> it has been a long while since I played with it
[16:55:09 CDT(-0500)] <EricDalquist> crap have to run