11–20 of 23 posts
Edge Chromium explicitly uses a new User-Agent string so websites see it as Chromium, not as Edge (it does not even contain "Edge", only "Edg").
And yet, Google intentionally works against any browser except their own.
Personally, I think this could just be chalked up to UA string parsing issues. Not worth the trouble for Google to kick up a storm over a marginal market share browser.
Google, who advocates for everybody else that you should use standards and proper feature detection, still relies on UA whitelists for their own products.
Then look at google.com homepage itself... not responsive, not in any way modern... many of their own sites perform terribly by their own guidance to other devs.
Google's hypocrisy is sickening and I'm tired of their "we own the web, do what we say" attitude.
Not sure if it was MS changing something or Google changing something?
Earlier quoted context omitted.
That's... not how the web is supposed to work.
Until the day 100% of browsers support 100% of features with 100% correct implementations, or we have only one browser, it will keep working like this.
Firefox mobile already pretends to be Chrome for several Google websites. Edge Chromium explicitly uses a new User-Agent string so websites see it as Chromium, not as Edge (it does not even contain "Edge", only "Edg"). And yet, Google intentionally works against any browser except their own.
Personally, I think this could just be chalked up to UA string parsing issues. Not worth the trouble for Google to kick up a storm over a marginal market share browser.
But the bigger point is why are they even sniffing UA strings? Google, who advocates for everybody else that you should use standards and proper feature detection, still relies on UA whitelists for their own products. Then look at google.com homepage itself... not responsive, not in any way modern... many of their own sites perform terribly by their own guidance to other devs. Google's hypocrisy is sickening and I'm…
You're video, audio API is quite mess!