False positive on Edge 17 when Chrome >= 51 is present
See original GitHub issueOur website doesn’t work on Edge 17 but the regex would say otherwise. Here’s a minimal browserslist config that should return false on Edge 17, but is true:
[
"chrome >= 51",
"edge >= 18"
]
Omitting the Chrome line returns false.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Virus/Malware: TROJ_FRS.VSNTE222
we are getting this message from every client since several minutes. Is it a false positiv error or do we have a real...
Read more >Chrome smoked by Edge in browser phishing test
For zero-hour phishing URLs, the results weren't quite as wide, but even here Edge started at 82% to Chrome's 59% and Firefox's 51%....
Read more >Microsoft Defender falsely detects Win32/Hive.ZY in Google ...
A bad Microsoft Defender signature update mistakenly detects Google Chrome, Microsoft Edge, Discord, and other Electron apps as 'Win32/Hive.
Read more >Microsoft mistakenly rated Chromium, Electron as malware
Microsoft mistakenly rated Chromium, Electron as malware ... Defender update fixed the mess after a weekend of false positive weirdness.
Read more >Google Chrome version history - Wikipedia
Google Chrome is a freeware web browser developed by Google LLC. The development process is split into different "release channels", each working on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just tested it, works. Thank you!
Anyway, all Chrome-based browsers should be detected as Chrome.