Re: Admin browser support policy
Django 1.11 dropped support for IE8 and below as those browsers are end of
life.
It looks like we could now drop support for IE<11 based on this from
Microsoft: "Beginning January 12, 2016, only the most current version of
Internet Explorer available for a supported operating system will receive
technical supports and security updates. Internet Explorer 11 is the last
version of Internet Explorer, and will continue to receive security
updates, compatibility fixes, and technical support on Windows 7, Windows
8.1, and Windows 10." [0]
Yes, I would say we care about mobile browsers. Django 2.0 will likely add
responsive CSS for the admin [1].
I'm not sure what "Does Safari deserve/require special casing?" means.
[0] https://www.microsoft.com/en-us/windowsforbusiness/end-of-ie-support
[1] https://github.com/django/django/pull/8610
On Wednesday, June 14, 2017 at 7:02:45 PM UTC-4, Curtis Maloney wrote:
>
> This topic seems to appear frequently over the years, but I've yet to
> see a clear decision.
>
> Without a clear Browser Support Policy for admin, it can be very unclear
> what cleanups, optimisations, and improvements can be made.
>
> Collin Anderson suggested supporting IE11+ ("as that's the latest on
> Windows 7 and there's not much 9-10 usage"), and I'd suggest also
> considering the general Google approach:
>
> Basically, it's "Current and Previous version", and considering IE as
> separate from Edge (so IE 10/11, Edge current and previous).
>
> Does this sound fair and reasonable?
> Do we care about mobile browsers?
> Does Safari deserve/require special casing?
>
> Once we can resolve this, I want to start working on revising all the
> JS. But I won't start that until I know what dross I have to still drag
> along.
>
> --
> Curtis
>
--
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/b7960cbc-0dfe-4547-b7ec-1a6dc6907f86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Admin browser support policy
I certainly care about mobile support. Being able to use even a limited
version of Django admin on my phone would make my life significantly better.
PJJ
http://philipjohnjames.com
On Wed, Jun 14, 2017 at 4:02 PM, Curtis Maloney wrote:
> This topic seems to appear frequently over the years, but I've yet to see
> a clear decision.
>
> Without a clear Browser Support Policy for admin, it can be very unclear
> what cleanups, optimisations, and improvements can be made.
>
> Collin Anderson suggested supporting IE11+ ("as that's the latest on
> Windows 7 and there's not much 9-10 usage"), and I'd suggest also
> considering the general Google approach:
>
> Basically, it's "Current and Previous version", and considering IE as
> separate from Edge (so IE 10/11, Edge current and previous).
>
> Does this sound fair and reasonable?
> Do we care about mobile browsers?
> Does Safari deserve/require special casing?
>
> Once we can resolve this, I want to start working on revising all the JS.
> But I won't start that until I know what dross I have to still drag along.
>
> --
> Curtis
>
> --
> 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 https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/django-developers/c03cd097-de5c-7538-2866-a989291b9a3e%40tinbrain.net.
> 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CACXM1yFuL13wX4g%2BrGt%3DE%3D8P29W1zw5iN00dgwUrq6KGqwieLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Admin browser support policy
This topic seems to appear frequently over the years, but I've yet to
see a clear decision.
Without a clear Browser Support Policy for admin, it can be very unclear
what cleanups, optimisations, and improvements can be made.
Collin Anderson suggested supporting IE11+ ("as that's the latest on
Windows 7 and there's not much 9-10 usage"), and I'd suggest also
considering the general Google approach:
Basically, it's "Current and Previous version", and considering IE as
separate from Edge (so IE 10/11, Edge current and previous).
Does this sound fair and reasonable?
Do we care about mobile browsers?
Does Safari deserve/require special casing?
Once we can resolve this, I want to start working on revising all the
JS. But I won't start that until I know what dross I have to still drag
along.
--
Curtis
--
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/c03cd097-de5c-7538-2866-a989291b9a3e%40tinbrain.net.
For more options, visit https://groups.google.com/d/optout.
