#11300: Switch to HTML5
---------------------------+------------------------------------------------
Reporter: spliter | Owner: spliter
Type: PLIP | Status: assigned
Priority: major | Milestone: 4.2
Component: Templates/CSS | Keywords:
---------------------------+------------------------------------------------
Comment(by alecm):
Thanks Denys, that's great news. Let me know if there's anything you need
from the FT to make sure your work is ready in time.
The one concern the framework team had during our last meeting was that it
would be best if Modernizr were actually used explicitly within Plone if
we're going to include it. To that end it would be a good idea to replace
the current IE specific CSS/JS using Modernizr techniques. This would
provide the following advantages:
1) Eating our own dog food and providing basic guidance for how to use
Modernizr in a Plone context
2) Possibly reducing the number of resources served to IE clients.
Does that seem like something you could include as part of the
implementation?
Also, do you feel there's a particular subset of Modernizr that we
could/should use to minimize payload, or would it be best to include the
full library?
--
Ticket URL: <http://dev.plone.org/plone/ticket/11300#comment:37>
Plone <http://plone.org>
Plone Enterprise Content Management System
_______________________________________________
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
https://lists.plone.org/mailman/listinfo/plone-plip-advisories
