-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Notify users that we are dropping support for their current browser #16283
Comments
The best way to do this is probably to utilize the home notification system, which you can see here: metamask-extension/ui/pages/home/home.component.js Lines 304 to 551 in c519d3e
We can add a new conditional notification that is only displayed for users of browsers that are planned to be deprecated soon. For now, we can use the range suggested in this PR, but this range will change over time. For reference, here is the live Storybook page for the Home notification component: https://metamask.github.io/metamask-storybook/?path=/story/components-app-homenotification--default-story Open questions:
|
When we were warning users about the deprecation of the test networks, we allowed the warning to be dismissible as it could get in the way of users doing important things, but the warning would re-appear once the user switched back to a test network that was going to be deprecated or closed and re-opened MM (annoying but hopefully effective). Maybe a similar approach could make sense here - for reference: #15725 What happens to an user if they continue to use their current unsupported browser? Will they loose access to MM or will they be stuck at the last MM version that supports that browser? |
Great question! MetaMask will continue working, but they won't be able to update MetaMask until updating the browser first.
Good example. I agree, a similar approach could work well here. It does make sense to allow the notice to be dismissed, but keep reminding the user about it. I wonder what interval we could use here though, as it's not tied to any user action. Maybe once per day, or something like that? |
OK, I think it makes the most sense for this to be a dismiss-able alert that comes back after some period of time. Providing no way to dismiss the notification would be unacceptably irritating, and we don't have a good justification for considering it. But it would also be unsafe and confusing if we never showed the user the warning again after the first dismissal. My remaining questions are:
|
For the copy, I think this is what we want to communicate:
|
Thoughts @bschorchit @Gudahtt? Proposed copy: |
Thanks @coreyjanssen ! That looks good to me, it has all of the information we wanted. The tone doesn't strike me as particularly urgent, but maybe that's OK. |
Had a discussion with @Gudahtt about alert intervals -- every other day would be appropriate as to not annoy users, but encourage them to update browser versions. |
We would like to notify users when we are planning to drop support for the browser they are currently using, so that users have at least once release to learn about this change and how it will impact them.
The text was updated successfully, but these errors were encountered: