Hey,

Looking at some browser market share stats
(http://www.sitepoint.com/browser-trends-august-2015-chrome-exceeds-50/
, disclaimer:
http://www.sitepoint.com/how-browser-market-share-is-calculated/) IE8
seems hardly be used anyway. Furthermore, with the dropped support for
IE8 (and 9+) on Jan 12th, 2016
(https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=internet%20explorer),
I don't really see any problem in removing IE8 support and notifying the
users that they have to update to a modern browser.

Therefore I find Aymeric's proposed solution "You are using an old web
browser ..." a reasonable choice over being stuck with ages old
technology that is long outdated.

/Markus

PS: I'd go with SVG solution

On Tue, Aug 18, 2015 at 04:13:11AM -0700, Tim Graham wrote:
I also had the idea of upgrading jQuery to jQuery 2 which drops support for
IE6/7/8, but I guess this will break all the JavaScript in the admin under
those browsers. Do you think that's unacceptable at this time? If so, could
you propose an alternate timetable for the upgrade?

On Tuesday, August 18, 2015 at 3:32:18 AM UTC-4, Aymeric Augustin wrote:

On 18 août 2015, at 01:28, Tim Graham <[email protected] <javascript:>>
wrote:

> Unless someone can present an argument for keeping IE8 support, I
wouldn't worry about it considering it will be end of life about 1 month
after the release of Django 1.9.

Let’s just make sure the admin stays usable, even if it looks bad. Since
we’re taking the SVG route, providing an alt text on icons should do.

We could be explicit about the lack of support for IE8 and lower by adding
a conditional message in the template:

<!--[if lt IE 9]><p class="error”>You are using an old web browser which
cannot display this page correctly. Please update to a more modern browser
or contact your system administrator for help.</p><![endif]-->

--
Aymeric.






--
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 [email protected].
To post to this group, send email to [email protected].
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/e541a69a-2ded-4af1-b049-f144878c0f83%40googlegroups.com.
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 [email protected].
To post to this group, send email to [email protected].
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/20150818113357.GA1859%40pyler.local.
For more options, visit https://groups.google.com/d/optout.

Attachment: pgpgFEniLPuy7.pgp
Description: PGP signature

              • ... Sam Cooke
              • ... Tim Graham
              • ... Marc Tamlyn
              • ... Josh Smeaton
              • ... Marc Tamlyn
              • ... Josh Smeaton
              • ... Tom Christie
              • ... Aymeric Augustin
              • ... Collin Anderson
              • ... Tim Graham
            • ... Markus Holtermann
      • ... 'Hugo Osvaldo Barrera' via Django developers (Contributions to Django itself)
        • ... elky
          • ... 'Hugo Osvaldo Barrera' via Django developers (Contributions to Django itself)
            • ... Tim Graham
  • ... elky
    • ... Collin Anderson
  • ... Curtis Maloney
    • ... Collin Anderson

Reply via email to