0
0
mirror of https://github.com/wagtail/wagtail.git synced 2024-12-01 11:41:20 +01:00
wagtail/docs/editor_manual/browser_issues.rst
2021-11-16 09:59:36 +00:00

32 lines
1.8 KiB
ReStructuredText
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Browser issues
~~~~~~~~~~~~~~
Some issues with Wagtail may come from the browser. Try `clearing the browser cache and cookies <https://www.refreshyourcache.com/>`_, or you can also try using Wagtail with `another browser <https://browsehappy.com/>`_ to see if the problem persists.
JavaScript is required to use Wagtail make sure it is `enabled in your browser <https://www.enable-javascript.com/>`_.
Supported browsers
__________________
For the best experience and security, we recommend that you keep your browser up to date. Go to `Browse Happy <https://browsehappy.com/>`_ for more information.
.. _ie11:
IE11
____
Wagtail has officially removed support for the legacy Internet Explorer browser in 2.15.
* In Wagtail 2.11 (LTS), there was be a warning message displayed on the Wagtail dashboard for IE11 users with administrator role.
* In Wagtail 2.12, the message was displayed to all users regardless of their role.
* In Wagtail 2.13 and 2.14, the message was displayed at the top of all pages.
* Wagtail will no longer support IE11 as of version 2.15 and beyond.
If this affects you or your organisation, consider which alternative browsers you may be able to use.
Wagtail is fully compatible with Microsoft Edge, Microsofts replacement for Internet Explorer. You may consider using its `IE mode <https://docs.microsoft.com/en-us/deployedge/edge-ie-mode>`_ to keep access to IE11-only sites, while other sites and apps like Wagtail can use modern browser capabilities.
Assistive technologies
______________________
We want Wagtail to be accessible for users of a wide range of assistive technologies, but are aware of many blockers currently. For an overview, see our `public accessibility audit <https://docs.google.com/spreadsheets/d/1l7tnpEyJiC5BWE_JX0XCkknyrjxYA5T2aee5JgPnmi4/edit>`_.