Google Forces Microsoft Edge Preview Users To Use Chrome For Modern YouTube Experience (thurrott.com) 137
An anonymous reader quotes a report from Thurrott: Microsoft started testing a new Microsoft Edge browser based on Chromium a little while ago. The company has been releasing new canary and dev builds for the browser over the last few weeks, and the preview is actually really great. But if you watch YouTube quite a lot, you will face a new problem on the new Edge. It turns out, Google has randomly disabled the modern YouTube experience for users of the new Microsoft Edge. Users are now redirected to the old YouTube experience, which lacks the modern design as well as the dark theme for YouTube, as first spotted by Gustave Monce. And when you try to manually access the new YouTube from youtube.com/new, YouTube simply asks users to download Google Chrome, stating that the Edge browser isn't supported. Ironically, the same page states "We support the latest versions of Chrome, Firefox, Opera, Safari, and Edge." The change affects the latest versions of Microsoft Edge Canary and Dev channels. It is worth noting that the classic Microsoft Edge based on EdgeHTML continues to work fine with the modern YouTube experience.
Comment removed (Score:5, Insightful)
Re: (Score:1, Informative)
Re: (Score:2)
Or maybe this is a site that aggregates IT news and I heard a rumour that MS is a pretty big company in that space. Though I could be wrong.
Nah, must be a shill.
Re: Who needs a "modern YouTube experience? (Score:2, Funny)
And don't forget the gnu hurd shills!
Re: (Score:3)
Yes, lets not forget either of the two of them!!!
just can't help themselves (Score:1)
The nazis who run Big Brother Google just can't help themselves. They NEED to abuse their monopoly power. It's who they are.
Re: (Score:1)
Perhaps it is time that some court helps them. These shenanigans look a lot like Microsoft pretending back in the day that Internet Explorer was an inseparable part of Windows.
This time, I think Microsoft might have a reason to sue. And despite of what I think of Microsoft otherwise, in this I would root for them...
Re: just can't help themselves (Score:1)
Re: (Score:1)
YouTube's not done till Edge won't run.
Re: (Score:3)
Not only that, but if you go to the link for the new version of YouTube, it prompts you to sign up to participate in user research studies for Google before you can access the new design. It's apparently an experimental design that is likely being rapidly iterated, rapidly broken, and isn't even ready enough to be put in front of the general public yet for A/B testing.
Mind you, I'm NOT AT ALL a fan of Google or Chrome, but I fail to see any issue with a company taking the perfectly reasonable step of only s
It's time to take the trash out (Score:4, Insightful)
Re: (Score:2)
We can start cleaning up the trash with Slashdot posters that vilify companies without having a clue what is going on.
It's not Google's fault Microsoft set the user agent string on their browser incorrectly. If I fire up Edge Dev10 and change the user agent string from "Edg\" to "Edge\" then Youtube works just fine.
Re: (Score:1)
As far as it is about the code, that is exactly the intent. The creator grants everyone the right to use it and redistribute it (albeit with certain restrictions in case of the GPL).
Re: It's time to take the trash out (Score:2, Interesting)
You mean just like Google took all the work Apple did on Webkit (the rendering engine for Safari), and adopted it for use in Chrome (Eventually Google started referring to its version of Webkit as Blink, but it came from Webkit code and initially kept the name)? Or like Apple took all the independent work done on the KTML web browser engine (I believe initially created by volunteers as part of a project to design a web browser for Linux enthusiasts using a KDE desktop) and created Webkit out of it?
That's k
time for "a day without google" (Score:2)
Every year we need a "no google day". Which day should we pick?
I think cyber monday would be impactful. But also not a good day to give up my google habit.
Maybe Groundhog day.
Re: (Score:2)
Sounds like a good idea, given how Google is more and more using these scummy tactics.
Re: (Score:2)
Re: (Score:2)
Why is it time for that? Because MS stuffed up their user agent in the latest Edge dev build and setting it back to saying "Edge" instead of "Edg" fixes stuff? Yeah, boycott Google!
See? (Score:2)
You all were so worried about Google wasting their scarce resources on cold fusion... but you didn’t need to worry. They’ve still got plenty of money to be evil with!
Future possible Edge not fully supported (Score:1)
Gee, Google not giving a 100% support to a dev version of Edge. Oh, the humanity.
Re: (Score:2)
Re: (Score:3)
Microsoft probably changed the user agent, or some other browser identifier. They are in the middle completely swapping out the rendering engine.
Re: (Score:2)
Yup. Google build in a check for a non-existent browser identifier in YouTube and then Edge suddenly started using that unknown identifier by accident.
Google can do no wrong.
Re:Future possible Edge not fully supported (Score:5, Informative)
Almost - Microsoft managed to change the identifier from "Edge/" to "Edg/", and Google's algorithm can detect what version of Edge it is because they are looking for "Edge/".
Note that you don't even need to drop the Edge version number down to a recognised number - you just need to correct the typo in "Edg/" to get the modern experience on Edge Dev.
Clearly, the modern experience is only enabled when a compatible user agent is found, with the old interface the default (for maximum compatibility) - one small typo is enough to prevent it being a recognise user agent.
Re: Future possible Edge not fully supported (Score:2)
This is what I was thinking too. Seemed more like user agent string issue than someone taking the time to block one version of Edge over another. Google isn't that stupid; it would be easily discoverable and cause bad PR.
Re: (Score:2)
Or they want to support devices / apps where delivering modern interface would cause a problem, so they default to the old interface and sniff for anything that is broadly compatible for the modern experience.
Re: (Score:2)
Or you can mess up the typo more. "Edh\" gives you the new Youtube experience as well.
I thought it was MS's fault at first too, but no, Google isn't Whitelisting Edge. It's blacklisting the Edge Dev build.
Re: (Score:1)
Lotus 1-2-3 and MS-DOS 6 comes to mind.
Re:Future possible Edge not fully supported (Score:4, Insightful)
Indeed.
Basically it is funny on one funny how such practices come back to bite you when others do things back to you.
But on the other hand sad that Google has embraced the dark side fully in the last few years after many years of flirting with it.
Re: (Score:3)
Supports Chrome, Firefox, Opera, Safari, and Edge (Score:3)
The summary mentions YouTube's new look fully supports at least:
Chrome
Firefox
Opera
Safari
Edge
They are evil for pushing consumers who want the dark theme to use - a browser, pretty much any browser.
Apple's browser they support fine, Microsoft's browser is fine, Mozilla's browser, some browser that acheived 10% market share 20 years ago - all fully supported.
YouTube also supports the test version of Edge which hasn't even been released, though thr browser that hasn't been released doesn't show the dark theme y
Re: (Score:2)
Why would you not support newer versions of a browser you support??
Hint.. Because you want them to change to Edge, because you are abusing your market position........
Re: (Score:2)
Hmm, why would you support, but not add new features, for a browser version that hasn't been released? Let's think about that.
Maybe an easier question - with all the security issues on the web and in browsers, why would you USE a browser version that even Microsoft says it's release ready yet?
Tell you what, how about we see what happens after Microsoft releases the new version of their browser? Until then, I'm not going anywhere near it.
Re: (Score:2)
Hmm, why would you support, but not add new features, for a browser version that hasn't been released? Let's think about that.
Maybe an easier question - with all the security issues on the web and in browsers, why would you USE a browser version that even Microsoft says it's release ready yet?
Tell you what, how about we see what happens after Microsoft releases the new version of their browser? Until then, I'm not going anywhere near it.
Let's see do more work and something unethical that would will be bad PR, or do no work, and be ethical..
so hard a choice, I wonder why ANYONE would take position two...
Huh? (Score:2)
Sorry, I'm having trouble parsing that sentence. I don't know if there is a missing or mistyped word perhaps? Maybe the punctuation is throwing me off.
Anyway, YouTube fully supports Edge (and every browser with more than 4% market share). When Microsoft releases a new version, we'll see if YouTube supports it.
Re: (Score:2)
Half your list (bolded for emphasis) they already killed. Or at least, they succeeded in forcing to be Chromium skins by killing native support for IE/Edge/Opera.
And Opera, in many ways, invented the modern web browser UX. Little things like "tabs".
Re: (Score:2)
wrong, you missed the problem. and that there is no problem, some crappy prototype version of edge that might not see the light of day doesn't work with "the modern youtube experience" (- as aside, that's shithead marketing speak)
modern YouTube experience. (Score:3)
Re: (Score:2)
It is a mistake. Microsoft's. Edge is whitelisted for the new Youtube interface. But the latest dev build lists the user agent string incorrectly. If you set it back to "Edge\" instead of "Edg\" then Youtube works just fine.
Re: (Score:2)
I correct myself: Make another typo in Edge such as "Edh" instead of "Edg" and it works fine. Google is actively targeting the dev build for whatever reason.
Re: (Score:2)
No they aren't - in fact both Google has fixed the browser detection to work with Microsoft's error, and Microsoft have pushed a fix to the error in Edge.
It looks like simply optimization - sniffing for "Edg" is more reliable than sniffing for "Ed", and faster than looking for "Edge" (about 25% faster, which is negligible on single access, but significant when you are handling millions of requests.
So it has classified the browser as something it needs to check the version of - but has been unable to parse t
More amusingly (Score:3)
User Agent? (Score:4, Insightful)
Seems silly to ask, but has anyone tried accessing NewTube in Edge after setting the user agent to Chrome?
Re: (Score:3)
Seems silly to ask, but has anyone tried accessing NewTube in Edge after setting the user agent to Chrome?
Yeah that works. You know what else works? Setting the user agent to Edge.
Currently my user agent on the latest dev build is "Edg/76.0.167.1" putting back the missing e makes youtube work just fine.
Re: (Score:2)
To reply to myself, "Ed" works and "Edh" works too, so Google IS specifically targeting the Edge dev build.
New motto: (Score:2)
Evil R Us
Re: (Score:1)
Yeah I'm sure you'd think that if you just take news articles at face value rather than researching what is going on, namely that MS isn't using a normal user agent string in the dev builds.
Re: (Score:2)
Thanks for reminding me not to believe summaries without further research.
This is a non-story. (Score:5, Insightful)
It is not unusual for web apps to check browser versions for optimization and compatibility purposes. The ephemeral versions of Edge are no doubt falling outside YouTube's expected range. Anyone using a developer build should be expecting this exact sort of quirk.
Re: (Score:1)
It is not unusual for web apps to check browser versions for optimization and compatibility purposes. The ephemeral versions of Edge are no doubt falling outside YouTube's expected range. Anyone using a developer build should be expecting this exact sort of quirk.
Literally any other site? I'd agree with you. But this site? Not so sure. Google playing silly buggers with youtube and Edge is one of the rumours about why this mess even started.
Let's try loading youtube.com/new with different user agents:
edge-chromium user agent string: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3800.0 Safari/537.36 Edg/76.0.173.0" doesn't work.
Chrome's "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chr
Re: (Score:2)
"It is not unusual for web apps to check browser versions for optimization and compatibility purposes."
Exactly. If the browser you use doesn't render HTML5 properly and doesn't support flash it's the users problem. If it does, just change your user-agent. Pretty simple. If the property owner does a redirect or interstitial LP warning users who's user-agent it doesn't care to support, that is their right. I mean you're not paying them.
There's actually no difference in this than the consistent pop-ups
Re: (Score:1)
It is not unusual for web apps to check browser versions for optimization and compatibility purposes. The ephemeral versions of Edge are no doubt falling outside YouTube's expected range. Anyone using a developer build should be expecting this exact sort of quirk.
Except that's not what is happening at all. Quite the opposite. Edge works just fine on Youtube, but the developer build does not identify itself as Edge. My current user agent string is: Edg/76.0.167.1 If I add in the missing e everything works just fine. MS Goofed.
Re: (Score:2)
bizarro slashdot (Score:5, Funny)
Re: bizarro slashdot (Score:1)
Just stay in that room, then.
Re: (Score:2)
Youtube? (Score:2)
Re:Youtube? (Score:5, Interesting)
Designed for ads, sure.
But in fact the only ads I see on youtube are the rare banner on front page to subscribe to heir paid service that the adblock does not apparently manage to suppress. Everything else in there is ad-free.
Adblockers, yey!
Re: (Score:2)
Why are you using the internet? Its designed to put ads in your face more so than Youtube is. Hell if you're in the USA you can't even use the internet at all without the ISP harvesting your data. Why don't you take your privacy more seriously! Hypocrite! Anger! *froth* RAGE
Re: (Score:1)
It was never designed for ads.
I live in a part of Europe where privacy is still valued - because, as part of the Soviet Union, they learned what life is without it.
Re: (Score:2)
I used Internet years before www was invented.
It was never designed for ads.
Ding ding ding. We have a winner. I used Youtube years before it started showing for ads. It was never designed for ads.
And nothing of value is lost (Score:5, Interesting)
In my opinion, the older Youtube user interface is better laid out and more user-friendly than the new one anyway ... despite lacking a dark mode.
I often view videos on Youtube while browsing in another window side by side: which the new interface isn't made for.
For instance, Youtube's older user interface allows me to have a smaller video player, and I don't have to scroll incessantly in an unmaximised window to get to a video's comment section.
I use a Greasemonkey script [greasyfork.org] to force the old interface in Chromium.
+1 (Score:2)
Good news, now instead of tweaking I can just use Microsoft Edge for correct Youtube experience :-)
Re: (Score:2)
And faster too. Is there a way to force it like in SeaMonkey and Firefox?
Do the ads work? (Score:2)
It's a typo in the user agent (Score:5, Informative)
In the current Edge Chromium, the user agent is listed as:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3800.0 Safari/537.36 Edg/76.0.167.1
Note the bit at the end "Edg/76"
The "old" edge has a correctly spelled "Edge/XX" user agent.
If you enter a custom user agent and simply correct the spelling to "Edge/76", then you get the modern YouTube interface.
Clearly the user agent detection algorithm for YouTube recognises that it is not Chrome, Safari or Firefox (as the user agent might hint at), but it also can't recognise and parse the Edge version, and therefore it doesn't see it as a browser that is capable of the modern experience.
Re: (Score:2)
In the current Edge Chromium, the user agent is listed as:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3800.0 Safari/537.36 Edg/76.0.167.1
Note the bit at the end "Edg/76"
The "old" edge has a correctly spelled "Edge/XX" user agent.
If you enter a custom user agent and simply correct the spelling to "Edge/76", then you get the modern YouTube interface.
Clearly the user agent detection algorithm for YouTube recognises that it is not Chrome, Safari or Firefox (as the user agent might hint at), but it also can't recognise and parse the Edge version, and therefore it doesn't see it as a browser that is capable of the modern experience.
So they are basically blocking anything Chrome compatible from getting a Chrome experience on purpose?
Re: (Score:2)
So they are basically blocking anything Chrome compatible from getting a Chrome experience on purpose?
There is Opera, and Vivaldi and about a dozen other Chromium based browsers out there. How many of those are blocked from getting the modern experience on YouTube?
As I explained, this is most likely NOT about blocking Chromium browsers, but that they have identified it as Edge - which, until very recently, will only have meant an EdgeHTML based renderer. And because the algorithm couldn't parse what version it is, it wouldn't determine that it was a minimum version required for the modern experience.
Anyway,
Re: (Score:2)
So they are basically blocking anything Chrome compatible from getting a Chrome experience on purpose?
There is Opera, and Vivaldi and about a dozen other Chromium based browsers out there. How many of those are blocked from getting the modern experience on YouTube?
All of them?
It's because of new Edge user agent (Score:4, Interesting)
Re: (Score:2)
Not fanboys, maybe just more knowledgable. You know that "Ed/76" works too, as does "E/76" and "Edh/76". It is *only* "Edg/76" that doesn't work.
Now whether or not there are legitimate issues with the latest dev build of Edge on Youtube that justifies this is a different question, but there is zero doubt that not only Google does recognise it, but treats it different from any other spelling mistake.
Re: (Score:2)
Re: (Score:2)
Presumably this is a quirk of an optimization / code path.
Look at it this way - first thing any parsing is going to do is identify what type of browser it is, then figure out what version it is.
It's common for user agents to contain multiple identifiers - in the case of Edge, it contains the strings for various other browsers (Mozilla, Chrome, Safari, etc.), so you need to look for something distinctive.
Looking for "E", and possibly "Ed", is not sufficient to identify the user agent as Edge. It's likely the
The chromocalypse is coming (Score:4, Interesting)
overreacting r us (Score:2)
When you have a new interface with limited QA vs an older interface that's known to be compatible with everything, you present the compatible interface when you can't recognize the client.
Re: (Score:2)
That's what I thought too, except changing the UA string to Edh or Ed or Edge or just E work just fine, it's only Edg that is treated differently.
$THING doesn't work in pre-release software (Score:3)
Still checking user agent? (Score:1)
Websites are still checking the user agent?!? I thought that was something only inexperienced or incompetent developers did.
Re: (Score:2)
Or developers so competent that they are using experimental features of their own browsers and thus differentiate them.
Re: (Score:1)
Then they should be using feature detection, not the user agent.
They must have fixed the issue.... (Score:2)
I noticed last night and earlier today that I could not turn on Dark Mode on YT with the new Edge dev version, but now that option is available and working.
So let me get this right... (Score:2)
...if I don't like it when Google messes up a perfectly good interface (as they have: News, Maps,...), if I open it in Microsoft Edge, I can use the old/ good interface? Yes, give me Edge!
Of course there will come a day...