This is on the staff interface.
On 19.11 sites using Internet Explorer 11 we have found 2 issues:
- /members/memberentry.pl make an edit to a patron record and click Save. The page does not save.
- If a user has checkouts, on /members/moremember.pl in the issues table no issues are displayed. Click on Always show checkouts immediately and no issues are displayed.
I marked this as Major as we still have customers with organisations restricted to using IE.
For what it's worth this problem doesn't seem to affect Microsoft's new Chromium-based version, Version 83.0.x, which my Windows computer installed without asking me.
(In reply to Janet McGowan from comment #0)
> This is on the staff interface.
> On 19.11 sites using Internet Explorer 11 we have found 2 issues:
> - /members/memberentry.pl make an edit to a patron record and click Save.
> The page does not save.
I'm inclined not to make accommodations for a browser which is so old. Internet Explorer 11 was first released in 2013. Since then two newer Microsoft browsers have been released: Edge in 2015, updated in 2019 to the Chromium-based version.
The latest version of Edge is available for Windows 7, 8, and 10.
> - If a user has checkouts, on /members/moremember.pl in the issues table no
> issues are displayed. Click on Always show checkouts immediately and no
> issues are displayed.
I could not reproduce this problem even in IE11.
Iirc we are not officially supporting IE for the staff interface, but only for the browser. But could only locate a note in the manual:
Is support of browser versions something we should discuss at the next meeting?
I'll be fixing this (sooner or later) locally, since we have many clients that use IE 11. (Many of these clients having their browser usage forced on them by corporate IT policies.)
I'll submit my patches here whether or not the community chooses to accept them.
Maybe we should default me as the Assignee for the "Browser compatibility" component, as I'm going to be supporting IE for as long as I work at Prosentient Systems.
Admittedly despite me saying that I'd look at fixing it, I haven't had the time, and based on the info from Owen, it might not be trivial to do such a fix.
Ok looking at this again...
Using https://babeljs.io/, it's suggesting the following.
I get support calls about this on a weekly basis, so I'm going to apply Bug 26305 locally, so that staff users get a warning that IE 11 won't work for them.