[PLIP-Advisories] [Plone] #11300: Switch to HTML5

Wed May 18 21:49:30 UTC 2011

#11300: Switch to HTML5
---------------------------+------------------------------------------------
 Reporter:  spliter        |       Owner:  spliter 
     Type:  PLIP           |      Status:  assigned
 Priority:  major          |   Milestone:  4.2     
Component:  Templates/CSS  |    Keywords:          
---------------------------+------------------------------------------------

Comment(by spliter):

 Replying to [comment:30 alecm]:
 > Having looked at the Modernizr docs, it looks like a pretty good idea to
 me.  However, if it's not required for implementing some aspect of the
 HTML5 transition, I'm not sure that it belongs here instead of in a
 separate PLIP.

 In order to complete this PLIP, we need to introduce support for HTML5
 elements in Internet Explorer. More reading on the topic —
 http://html5doctor.com/how-to-get-html5-working-in-ie-and-firefox-2/. Even
 though we are not going to introduce any new HTML5 elements now, the end
 integrators will do so and Plone should support the elements out of the
 box. Hence we need a shim to provide the support in IE. There are 2 ways:

   * we add shim-only JS (like http://remysharp.com/2009/01/07/html5
 -enabling-script/)
   * we add Modernizr that has shim integrated together with other
 features.

 At some point Modernizr should be part of Plone in my opinion. So,
 integrating separate shim and then, hopefully, Modernizr doesn't really
 make sense to me if we can integrate Modernizr now and get the shim.

 > Similarly, I'm not sure it makes sense to PLIP it on its own unless the
 PLIP provides some specific ways that Plone can make direct and immediate
 use of Modernizr features.  If it's just something people can use to help
 implement better HTML5 themes and content (e.g. compatible across
 browsers), then it may be best to just create an add-on that installs it
 in Plone (similar to collective.js.jqueryui).

 Modernizr does provide features that Plone might start using right away:

   * aforementioned HTML5 elements support in IE
   * special CSS classes on <html> element for writing IE-specific styles
 that are valid CSS (not, silly "* html" hacks). With this we could
 deprecate ie.css an ie.js (or whatever they are called) since both of
 those can take advantage of the CSS classes.
   * In addition we get the main feature of Modernizr — feature detection.
 This lets us build future proof application that just get better and
 better over time when browsers support more and more of HTML5 natively.

 Second point requires main_template.pt changes so, integration of
 Modernizr through an add-on doesn't feel like the right thing to do.

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/11300#comment:31>
Plone <http://plone.org>
Plone Enterprise Content Management System