For jQuery support in older browsers it's pretty simple to include jQuery 1.11 in old IE using conditional comments - that way we retain support with just an extra line of code, don't leave IE8 behind, and get the performance boost of jQuery 2 in modern browsers. As far as I'm aware they are still API compatible.
On Wed, 19 Aug 2015 at 08:23 Josh Smeaton <josh.smea...@gmail.com> wrote: > I agree with Shai. There are certain companies that have bought extended > support for WinXP/IE8 for extravagant amounts of money. That means > Microsoft is taking on the burden of support (security) for those systems. > They are EOL as far as we're concerned. We shouldn't intentionally cripple > support unless there is a reason to do so though. For example, unless we > need jQuery2 for some purpose, maybe it's best we just leave it at it's > current version for the moment. As for font/svg icons - alt text is fine > for an old browser out of support. > > > On Wednesday, 19 August 2015 09:25:38 UTC+10, Shai Berger wrote: >> >> On Tuesday 18 August 2015 14:29:15 Marc Tamlyn wrote: >> > I don't know about schedule, but caniuse reports IE8 browser usage at >> 1.5%, >> > more than IE9 or IE10. >> > >> > There's an argument we shouldn't be "enabling" people still using XP >> who >> > are stuck on IE8, and this is a decreasing problem, but I don't think >> we >> > can tie ourselves to Microsoft's support dates. >> > >> >> Sure we can, in the same sense that we "tie ourselves" to the support >> dates of >> PostgreSQL, MySQL and Oracle. >> >> 1.9 is the release following an LTS -- the perfect time for changes such >> as >> JQuery 2 and dropping support for old browsers. If developers need to >> support >> the legacy IE8, they can use Django 1.8. >> >> The suggestion to add a notice for IE8 users seems reasonable to me, but >> I >> don't think we should hold back progress just to keep the admin usable on >> it. >> >> Shai. >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/4c5a22ab-ee67-46d3-a82b-18f6ebea3c39%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/4c5a22ab-ee67-46d3-a82b-18f6ebea3c39%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyx3A30C60U5B%2BfJRm%3D_VPYoEN1j2uAMCW8BjftHtio7DcaeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
