You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
window.navigator.userAgent of the browser is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36
This is the UA string I'm seeing for the latest beta of chromium-based Edge running in Windows 10 in a virtual machine on my macbook. I noticed in this issue's discussion (#311) there is talk about a Edg value being present in the UA string, but I don't see it here. I do see it in a Canary build, as seen here: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4003.0 Safari/537.36 Edg/81.0.381.0. What's also interesting is that in both cases, Bowser is telling me the browser name is Chrome.
For reference:
This raises two questions for me:
Is the Edg flag update just lagging behind Canary and hasn't made it into beta yet?
I would expect Bowser to tell me that this browser is still Edge, but be able to differentiate between legacy and chromium-based versions by either bowser version number, the presence of blink: true, or both. Is this a bug in the Bowser library, in that it should be designating this browser as Edge, or do I need to check version/blink and not just rely on browser name for chromiun-based Edge detection? Happy to help fix if it is a valid bug.
The text was updated successfully, but these errors were encountered:
window.navigator.userAgentof the browser is:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36This is the UA string I'm seeing for the latest beta of chromium-based Edge running in Windows 10 in a virtual machine on my macbook. I noticed in this issue's discussion (#311) there is talk about a
Edgvalue being present in the UA string, but I don't see it here. I do see it in a Canary build, as seen here:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4003.0 Safari/537.36 Edg/81.0.381.0. What's also interesting is that in both cases, Bowser is telling me the browser name isChrome.For reference:
This raises two questions for me:
Edgflag update just lagging behind Canary and hasn't made it into beta yet?blink: true, or both. Is this a bug in the Bowser library, in that it should be designating this browser as Edge, or do I need to check version/blink and not just rely on browser name for chromiun-based Edge detection? Happy to help fix if it is a valid bug.The text was updated successfully, but these errors were encountered: