Switching to the HTML5 doctype won't hurt IE6 rendering (having dealt with
this myself several times). To the best of my knowledge--from my own tests
and third-party sources--using the new input attributes also doesn't hurt
IE6. However, if we start delving deeper into HTML5 and using the new HTML5
elements, etc. we will definitely hit problems very quickly. Techniques for
solving those problems are pretty readily available these days, but I don't
think we have any reason to go there right now.
All the same, I'd still rather give people the choice and ability to change
output rendering rather than simply making a unilateral change. I'd love for
our default to be the modern choice as long as it's an easily changeable
option!
But hey, aren't we starting to stray into... ::gasp:: front-end territory
here?! Where's our Benevolent Designer For Life? ;-)
All the best,
- Gabriel
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
