To see what's required, I made a pull request for jQuery 2 here: https://github.com/django/django/pull/5155
The selenium and JavaScript tests pass without any modifications to the admin's JavaScript. My own opinion is that if you really need IE8 support, it's not difficult to write a custom template and conditionally include the old jQuery version. If we view the admin as an internal management tool for "staff users", I think it's reasonable for organizations to know what browsers their staff uses and be able to make these determinations. For me, moving to jQuery 2 is a bit like the Python 2/3 debate. As long as we have to support Python 2/jQuery 1.x we are somewhat restricted in reaping the benefits of Python 3/jQuery 2. I'm not sure there are any new features in jQuery 2 at this time - the main benefit seems to be smaller size. Of course, if we start using new features of jQuery 2 at some point, we might break the solution proposed in the previous paragraph, but that seems okay to me since the point is that we shouldn't spend much time caring for unsupported browsers. If we don't want to use end-of-life dates for deciding a browser support policy, then what alternative metric should we use? On Wednesday, August 19, 2015 at 5:59:21 AM UTC-4, sdcooke wrote: > > I meant jQuery 2 and 1.11 are API compatible - you're right though, the > latest versions of jQuery might have deprecated things that are currently > used in Django. > > On Wed, 19 Aug 2015 at 10:39 elky <manse...@gmail.com <javascript:>> > wrote: > >> >> On Wednesday, 19 August 2015 14:27:53 UTC+5, sdcooke wrote: >>> >>> and get the performance boost of jQuery 2 in modern browsers. As far as >>> I'm aware they are still API compatible. >>> >> >> We should carefully check jQuery change log. I remember they removed >> toggle method in one of the latest versions, so some apps may broke because >> of that. >> >> -- >> 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-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> 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/446e9038-0b45-4a67-8b14-8cb402722f4b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/446e9038-0b45-4a67-8b14-8cb402722f4b%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/614e5159-b51f-424b-8551-753466cebbbb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
