Forum Discussion
MS Edge Chromium? or Chrome?
Dennis5mile By looking at your images they does not seems to be a Chrome an Edge issue.
- The first one is a message from Facebook itself, who believes you're using the Chrome browser, so nothing to be done by Microsoft on that case, you could try to contact Facebook about it and ask them to properly identify the browsers or just change the expression Chrome by browser.
- The second one one seems to be a message from a browser extension that you have installed (seems to be MS Office related). If the extension was installed from the Microsoft store then you are right to comply to Microsoft, but you need to comply with the extension creator team. If the extension was installed from the Chrome store then there's nothing that Microsoft could do about it, you could try to contact the extension owner and ask him to properly identify the browser and display the correct message for each case or like I already suggested just remove the Chrome reference or replace it by browser.
To be clear, this data is provided by Edge Insider. It's a conscious choice; they've set the user agent (i.e., the signal that tells everyone else what browser this is).
I won't presume what name Microsoft will use, but Edge Insider calls itself part of the "Chrome" family and likewise includes Chrome in its user-agent string.
I do hope this gets fixed properly: call Edge Edge. It's absolutely confusing to mainstream users to see "Chrome", so I hope they squash this bug instead of letting it seep into the official builds.
https://www.whatsmyua.info/
ikjadoon Microsoft already explained that they will use `Edg` instead of `Edge` to differentiate it from
the classic version, look for "User Agent String" in https://blogs.windows.com/msedgedev/2019/04/08/microsoft-edge-preview-channel-details/ for a detailed explanation.
From all the engines listed on https://www.whatsmyua.info/ just one does not have the fix to properly recognize the new Edge and I created an issue for it:
https://github.com/3rd-Eden/useragent/issues/143<- I created this issue so the library could be updated to properly identify the new Edge
https://github.com/faisalman/ua-parser-js/pull/375 <- There's already an issue for it and the they have an open PR with the fix.
https://github.com/bestiejs/platform.js/pull/170 <- They already merged the code fix to properly identify the new Edge.
Having said that, I do agree with you that Microsoft needs to stop pretending to be Chrome ( https://www.bleepingcomputer.com/news/microsoft/the-new-microsoft-edge-sometimes-impersonates-other-browsers/ )... If you take a look at the current Edge Dev (76.0.152.0) online config file, it overrides the user agent to pretend be Chrome for some sites, just look for user_agent_override:
https://config.edge.skype.com/config/v1/Edge/76.0.152.0?osname=win&channel=dev&clientId=[id]&osver=10.0.18875&osarch=x86_64&osring=WIF&osedition=professional&ostelemetrylevel=full
cbomtempo wrote:Having said that, I do agree with you that Microsoft needs to stop pretending to be Chrome
Thanks to so many websites doing UA sniffing for entirely the wrong reasons (trying to detect what features to enable in a given browser), this can't really happen while still expecting sites to work normally. While it can be argued that this is the website's problem, they're also not going to change, and that's the world we live in.
- The user agent contains a ton of information. Not Just "Chrome", but also Safari and Mozilla. It tells the website what the browser is capable of. Whatsmyua is taking the wrong guess and thinking it's Chrome. It's wrong.
Go here and they will guess it correctly:
https://developers.whatismybrowser.com/
