OK, by the power vested in me, I declare the admin unshackled from the need to support IE6.
Reception and dancing shall follow. On Thursday, June 9, 2011 at 2:22 PM, Carl Meyer wrote: > On 06/09/2011 05:32 AM, Idan Gazit wrote: > > I'm looking at admin tickets, and I realize that some defined policy > > for when we can safely start to break IE6 would be very helpful. > > > > I'd like to simply declare that going forward, the admin need not > > work perfectly in IE6. That leaves our support footprint for the > > Admin at "modern browsers" + IE>7. > > > > * contrib.admin is contrib, and thus not covered by Django's > > deprecation policy > > > > * This isn't a change which affects any other frontend product built > > with Django. The only audience this affects is users of the admin. I > > think it's reasonable to require administrative users to have IE7 if > > all they have is IE. > > > > The admin is already using the HTML5 doctype (see > > https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for > > background), but not any of the new HTML5 elements. > > > > This change would mainly open up the ability to use PNGs and remove > > hacks and workarounds from admin CSS/HTML > > > > Any objections? > > Hearty +1 from me, for purely pragmatic reasons. In 2011, IE6 support is > simply an unreasonable burden to place on volunteer front-end > development work, IMHO. It's hard enough getting front-end work done > without tripling (quadrupling? more?) the pain factor like that. In my > mind, asking front-end developers to support IE6 is roughly similar to > asking Python devs to support Python 1.5, perhaps not in terms of usage, > but in terms of the additional development pain. > > I think it needs to be stated clearly that the effective choice is > between maintaining IE6 support and making major improvements to the > admin. If someone wants to argue that admin IE6 support should be > maintained for another release, they should acknowledge that the > implication is that there probably won't be significant upgrades to the > admin UI for at least that long. > > If there are Django deployments whose administrators really can't use > any browser other than IE6, Django 1.3 will be around as long as they > need it. It's not a reasonable tradeoff for that (frankly somewhat > ridiculous - IE6 is how many years old now?) edge case to continue to > hold the rest of the community hostage. > > Carl > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
