21–30 of 207 posts
Basically Google doesn't allow development build Edge users to browse the preview YouTube? Doesn't seem like someone at Google hates Edge, just looks like they didn't test their brand new YouTube on every browser yet so just limited it to heavy Chrome users. Or am I wrong?
I hate this, though it is a kind of poetic justice for the way Windows 10 fights tooth and nail to keep you from switching your default browser away from Edge.
What exactly do you mean by "fights tooth and nail"? I had to reinstall my laptop a few months ago, and the experience was "navigate to Firefox download site, download, install, set default browser"... Same as it has ever been.
* when switching default browsers, Windows suggests you give Edge a try instead
* at some point I got a Windows notification suggesting that I try Edge instead of the browser I was using
IIRC they used to nag users more in the past but I think the notification I got also included an option to not be reminded again.
User agent for Edge-Chromium is a bit of a mess. Usually it identifies as "Edg", sometimes as Chrome, and sometimes as Edge (the old one). Specifically, that old Edge agent comes up for streaming sites because old Edge has different DRM systems and was able to serve 4K streams from Netflix and others, which Chrome did not do. New Edge still has those capabilities, so it doesn't want to be served the Chrome compatible…
For reference:
Automatic user-agent in Edge (Trident engine):
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.18362
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3739.0 Safari/537.36 Edg/75.0.109.0I hate this, though it is a kind of poetic justice for the way Windows 10 fights tooth and nail to keep you from switching your default browser away from Edge.
What exactly do you mean by "fights tooth and nail"? I had to reinstall my laptop a few months ago, and the experience was "navigate to Firefox download site, download, install, set default browser"... Same as it has ever been.
It's scummy and it's insulting.
The polymer UI does seem to work perfectly if you set the user-agent to Chrome Windows in devtools -> network conditions.
I'm surprised Google still uses useragent parsing for browser detection.
I wonder if they are using browser detection instead of feature detection. I don't know when YouTube started feeling so sloppy with it's coding (Gmail has also started feeling this way as it went very JS heavy). I am sightly biased against most JS in the presentation layer
Earlier quoted context omitted.
What exactly do you mean by "fights tooth and nail"? I had to reinstall my laptop a few months ago, and the experience was "navigate to Firefox download site, download, install, set default browser"... Same as it has ever been.
Off the top of my head: * when switching default browsers, Windows suggests you give Edge a try instead * at some point I got a Windows notification suggesting that I try Edge instead of the browser I was using IIRC they used to nag users more in the past but I think the notification I got also included an option to not be reminded again.
2 attempts from Microsoft... not so bad.
Having a blacklist of tested browsers you know to be so incompatible that the site is unusable for them would be even better.
But the optimal course would be that if a browser is not on your whitelist, you show a warning but allow the user to decide to give it a try nevertheless and have an option to go back to the degraded but more compatible legacy version of the site.
I understand building your intranet tool to only work in a small range of handpicked browsers or devices. But we're talking about a public video platform by a multi-billion dollar company with billions (well, 1.9 bn last I heard) of monthly active users.