How about delivering http://www.modernizr.com/ library. In my case it solves all problems with non existing tags (nav, section, header, article, footer) in such browsers as IE.
We ship jQuery with admin, why not use modernizr to support legacy browsers. I am positive, about input types fallback to text. I have tested this for a long time and it works. Generally speaking converting contrib apps to html5 would be a very good idea! Most django deployments does not depend on whether it has html4 or 5. Those who stick with 4, should have the same functionality provided by fallback in their browsers, however the largest part of the remaining group should benefit from transition. Google dropped support for IE6 legacy browsers more than year ago! http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Even microsoft wants IE6 dead http://ie6countdown.com/ I think we should join this movement, and provide modernizr, for example in conditional css tag <!--[if IE 6]> <script type="text/javascript" src="js/modernizr.js"></script> <![endif]--> It works for me, hence all should benefit from it. -- Matt Harasymczuk http://www.matt.harasymczuk.pl -- 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.
