Skip to content
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.

Sign up for GitHub

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

docs: Add browser support guidelines #23457

Merged
merged 1 commit into from
Mar 14, 2024
Merged

docs: Add browser support guidelines #23457

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,6 +229,7 @@ Whenever you change dependencies (adding, removing, or updating, either in `pack
- [Developing on MetaMask](./development/README.md)
- [How to generate a visualization of this repository's development](./development/gource-viz.sh)
- [How to add new confirmations](./docs/confirmations.md)
- [Browser support guidelines](./docs/browser-support.md)

## Dapp Developer Resources

Expand Down
14 changes: 14 additions & 0 deletions docs/browser-support.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Browser Support

MetaMask's browser support policy is to support:

* The last two years of Chrome stable releases
* The current and previous Firefox Extended Support Release

We try to support browser forks as well (aligned with supported Chrome/Firefox releases), but we don't actively test them.

## Providing notice of minimum supported version changes

Additionally, before bumping our minimum supported browser versions, we should always notify users in the application first. Otherwise users of older browser versions would unknowingly get stuck on old MetaMask versions, even if they had automatic updates enabled.

We have a home screen notification already for this purpose. All we need to do us update the `OUTDATED_BROWSER_VERSIONS` constant in the release prior to the minimum version bump, and all affected users should be notified in-app.
Loading