May 28 2019 05:08 AM - edited May 28 2019 05:25 AM
Hello,
I Noticed this Morning that I had returned to the old UI of Youtube.
When I go to https://www.youtube.com/new it is said that the Browser is not compatible and suggests me to use Google Chrome (Ha Ha). Yet It was working well until yesterday and my build of Edge (Dev Channel) does not seems to have updated....
Does anyone have the same problem ?
Is it the same thing than for the 'Google Meet' story ?
EDIT: Once again, changing User Agent throught the inspector for 'Chrome - Windows' fixes the issue.
May 28 2019 07:46 AM - edited May 28 2019 07:47 AM
@apprenti90 I'm also having the same issue and I'm glad to see it's not just me. Hopefully, the next update will incorporate whatever changes Google made to the site code.
May 28 2019 08:24 AM
May 28 2019 08:33 AM
@apprenti90 Noticed the same thing. Also, youtube studio is not working at all.
May 28 2019 08:49 AM
I do not think they are really "idiots" per se. They know what they do. :-). @Octavian20604
May 28 2019 09:05 AM
For everyone that is having this problem (i'm included) just use this extension https://chrome.google.com/webstore/detail/user-agent-switcher-and-m/bhchdcejhohfmigjafbampogmaanbfkg
May 28 2019 09:14 AM
May 28 2019 09:22 AM
May 28 2019 01:30 PM
We are aware of this issue and are working with the site owners to get it addressed. Thank you for taking the time to try out the Insider channels of Microsoft Edge.
May 28 2019 02:17 PM
May 28 2019 03:20 PM
@apprenti90
Yes, same here both, Dev & Canary. If I wanted Chrome, would have had it long ago. "HA HA" is right.
YouTube is ok, but, not YTNew
And, there is another issue! There settings available in YT are VERY different if using Edge or Edge C; including, YT in Edge C has no Dark Mode. BTW, it's the same whether YT or YTNew.
YTNew DOES work fine in Edge. Just not Edge C.
Cheers,
Drew
May 29 2019 05:13 AM
I'm guessing this is occurring across YouTube as a whole.
And now for other services by Google!
May 29 2019 11:16 PM
May 30 2019 03:59 AM
SolutionSeems to be fixed.
Thanks a lot :)
May 30 2019 03:59 AM
Solution