-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update our browser support strategy #2718
Comments
I started writing a document (internal only) positing various methods that we could determine future browser support. |
We've unpacked the work needed to come to a decision on future browser support. It's kept in a Trello board which isn't open, but we'll add discrete actions to the team board. |
Main things left to do:
|
README details are within the Browser and assistive technology support section
|
Gonna call this done! |
What
We're looking to move to a graded system for defining the support received by the different browsers out there. This system will define not only in which browsers features run, but also the level of testing we intend to do with them and the priority we'll give to bugs.
Why
Currently Frontend uses specific versions of particular browsers to determine the minimum level of browser support and what polyfills/prefixes are needed: principally Internet Explorer 8 and Safari 9, which indirectly provide support for older versions of 'evergreen' browsers.
As we transition into reducing support for IE11, and dropping all supporting for IE8–10, we want to reassess how we decide how our minimum level of browser support will work in a world where we only (or mainly) support evergreen browsers.
Who needs to work on this
Developers, content designers
Who needs to review this
Developers, content designers
Done when
Tasks
The text was updated successfully, but these errors were encountered: