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.

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

Chrome legacy check is broken for v100+ #4869

Closed
GaurangTandon opened this issue Mar 7, 2022 · 1 comment · Fixed by #4883
Closed

Chrome legacy check is broken for v100+ #4869

GaurangTandon opened this issue Mar 7, 2022 · 1 comment · Fixed by #4883

Comments

@GaurangTandon
Copy link

GaurangTandon commented Mar 7, 2022

Description

Chrome legacy check is broken for v100+.

Environment

  • Slate Version: any
  • Operating System: any
  • Browser: Chrome v100 beta that was released last week (Chrome Canary v101 also shows the bug)

Context

export const IS_CHROME_LEGACY =

Chrome 100 is marked as IS_CHROME_LEGACY = true, even though it is not a legacy browser.

@GaurangTandon
Copy link
Author

While fixing this bug, it would be a good idea to update legacy check for all browsers as they are updating to v100+ at the same time.

https://www.forbes.com/sites/gordonkelly/2022/02/19/google-chrome-microsoft-edge-mozilla-firefox-web-browser-update-warning

always-maap added a commit to always-maap/slate that referenced this issue Mar 11, 2022
dylans pushed a commit that referenced this issue Mar 14, 2022
* fix chrome and edge three digit version check #4869

* add changelist
DougReeder pushed a commit to DougReeder/slate that referenced this issue Apr 3, 2022
* fix chrome and edge three digit version check ianstormtaylor#4869

* add changelist
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant