Forum Discussion
TrueGame
Oct 20, 2020Iron Contributor
Microsoft websites detects Edge browser as Chrome hahaaha
Seriously? Please fix........
HotCakeX
Oct 24, 2020MVP
That store was stupid but I don't think Edge users should hide behind Chrome's user agent. knowing which browser you are using is nothing compared to all the data websites and trackers can get from visitors. (e.g your time zone, IP address, which website you came from, installed fonts, OS and version etc)
in this case, Microsoft's website apparently hasn't added support for the new Edge user agent yet.
in this case, Microsoft's website apparently hasn't added support for the new Edge user agent yet.
Wittycat
Oct 24, 2020Steel Contributor
It's not hiding, it preventing Google to do add "bug" to it's concurrent, even Vivaldi now stop to add their user-agent since on google services "bugs" occur only when the user-agent is different than Chrome.
In my case i don't care i don't use Google (and i even a blocklist to block all Google services (except ajax api used by too many dev to just "block" it).
For mobile i'm on Apple so Google i really don't care but some other user of Edge if they receive a bug from Google they will say it's because of Edge "because on Google chrome it work".
In my case i don't care i don't use Google (and i even a blocklist to block all Google services (except ajax api used by too many dev to just "block" it).
For mobile i'm on Apple so Google i really don't care but some other user of Edge if they receive a bug from Google they will say it's because of Edge "because on Google chrome it work".
- HotCakeXOct 25, 2020MVP
It's Google's fault that do it, Edge doesn't need to change anything or hide behind other user agents. when Google does something ill-intentioned like that everybody calls them out, it will just be a shame for them.
if they wanna bring shame upon themselves let them do it
- WittycatOct 24, 2020Steel ContributorOne example from the past, Google Earth blocked on Edge, because the browser was too old.
Browser who use the very same chromium it was a "BUG".
If Google have done it one, nothing prevent them from redo something like that - HotCakeXOct 24, 2020MVPI don't understand what you mean by "adding bug to its concurrent"