Opened 5 years ago

Closed 4 years ago

Last modified 4 years ago

#31032 closed Cleanup/optimization (fixed)

Document the minimal supported version of browsers for the admin

Reported by: Claude Paroz Owned by: Carlton Gibson
Component: contrib.admin Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no

Description

This current FAQ entry states:
The admin provides a fully-functional experience to YUI’s A-grade browsers, with the notable exception of IE6, which is not supported.

I think it's outdated because more recent versions of IE are currently not fully supported, especially since the responsive patch.
Can we find a way to indicate something more specific without having to list versions of all possible browsers? It would be great for Django admin devs to know which JS API they can use or not.
Read also this django-developers discussion.

Change History (12)

comment:1 by Mariusz Felisiak, 5 years ago

Triage Stage: UnreviewedAccepted

comment:2 by Tom Carrick, 5 years ago

Personally I'd be in favour of keeping this quite modern, as Curtis mentions in the discussion, perhaps the most recent couple of versions as of the release date for that particular Django version.

I'd also be in favour of using this as an impetus to clean up some of the old js, and perhaps we can even remove the old date/time picker code and rely on the browsers' native implementations.

This might frustrate users that have to target old browsers, but I think in general it should be reasonable to constrain people who use the admin to modern browsers. On the other hand, I also don't want this to be a reason for people to not update Django.

comment:3 by Ata Öz, 5 years ago

Owner: changed from nobody to Ata Öz
Status: newassigned

comment:4 by Mariusz Felisiak, 5 years ago

Has patch: set
Patch needs improvement: set

comment:5 by Carlton Gibson, 4 years ago

Ref #31309, no specifics but it looks like we're already incompatible with IE 11.

comment:6 by Carlton Gibson, 4 years ago

Owner: changed from Ata Öz to Carlton Gibson

comment:7 by Carlton Gibson, 4 years ago

comment:8 by Carlton Gibson, 4 years ago

Triage Stage: AcceptedReady for checkin

comment:9 by GitHub <noreply@…>, 4 years ago

Resolution: fixed
Status: assignedclosed

In 8b30360:

Fixed #31032 -- Updated admin browser support FAQ for 2020.

Following web standards, the modern _evergreen_ browsers are all
supported. This applies equally to mobile platforms. Assuming current
trends continue, this should be a sustainable policy.

Microsoft deprecated all versions of Internet Explorer. IE 11, the last
version, is described as a "compatibility solution" rather than a web
browser. Whilst it will receive security updates for the lifetime of
Windows 10 it's use is actively discouraged.

The IE 11 downloads page makes it clear: "We recommend you use the new
Microsoft Edge".

comment:10 by GitHub <noreply@…>, 4 years ago

In f982f0bd:

Refs #31032 -- Removed unsupported browsers workarounds and comments in admin's JavaScript.

Since 8b30360322d4de6687e17ab267a856db4e3c78a6, the admin documentation
is explicit that only modern evergreen browsers are supported. This
allows removing several long standing workarounds for IE and Opera older
versions.

Since 2013, Opera is based on the Chromium blink engine.

comment:11 by GitHub <noreply@…>, 4 years ago

In 29e35b9:

Refs #31032 -- Removed unnecessary vendor prefixes from admin CSS.

The CSS properties have been standardized and are available in all
supported browsers.

comment:12 by Claude Paroz <claude@…>, 4 years ago

In 909b5cd1:

Refs #31032 -- Removed obsolete CSS workaround for IE in openlayers template.

Note: See TracTickets for help on using tickets.
Back to Top