User tests: Successful: Unsuccessful:
See #37900 .
This PR removed the "Warning! Internet Explorer should not be used for proper operation of the Administrator Backend." message completely from the backend.
Code review or check the backend login with brocken CSS
Message is displayed (also if CSS is broken)
No message ever
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org: joomla/Manual#51
No documentation changes for manual.joomla.org needed
Status | New | ⇒ | Pending |
Category | ⇒ | Administration Language & Strings Templates (admin) Repository NPM Change |
Labels |
Added:
Language Change
NPM Resource Changed
Maintainers Checked
PR-4.3-dev
|
Well even when IE11 is EOL its still used in the wild not sure whether it makes much sense to remove it now. J5 a few months from now would be where i would remove such a message as that is a major with possible also more changes on the backend template site etc.
+100
Nothing has changed in our code to justify removing the error message. Joomla admin still will not work with internet explorer but with this PR no one will know that the browser is the cause of the problems and will now think Joomla is broken.
Internet Explorer is still in use even if it is eol and a user should be told when they get an error.
Just because in the wealthy western web the usage of IE has dropped below 1% does not mean that it is true globally.
For example in Iran, where joomla is heavily used due to our almost unique, support for the jihali calendar ie usage is still over 8% https://gs.statcounter.com/browser-market-share/desktop/iran
There are many other countries where Joomla is actively used where the % is 5% or over.
Title |
|
Labels |
Added:
PR-5.0-dev
Removed: PR-4.3-dev |
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-10-22 16:09:12 |
Closed_By | ⇒ | HLeithner |
Thanks
Thank you
Well even when IE11 is EOL its still used in the wild not sure whether it makes much sense to remove it now. J5 a few months from now would be where i would remove such a message as that is a major with possible also more changes on the backend template site etc.