Unpopular opinion: If it works in the engine that 70+% of devices are using, then it works. If it doesn't work in your non-Chrome browser, then your browser is what's broken.
Enkers@sh.itjust.works 1 week ago
Lemme guess: it works perfectly fine in chrome. Google has been using this sort of anticompetitive tactic for years to wage war against other browsers.
Chozo@fedia.io 1 week ago
Zerot@fedia.io 1 week ago
Except that it has been found in the past that Google/YouTube has been serving different html to Firefox than to Chrome. If they would be serving the same html, then you might have a point. But even then, Google can push through non standard changes to both chrome and YouTube before Firefox even has had a chance of making it compatible.
Chozo@fedia.io 1 week ago
For what it's worth, the bug in this article is partially replicable in Chrome, and isn't even unique to YouTube. Due to the way I keep my windows positioned, I sometimes get the mobile layout of a web page on my desktop because I opened it in a narrow window, and quite often those sites will go into the same flickering, rapid loop of layout adjustments the article describes. I ran into this quite often while I was applying for jobs last year.
Though I've not seen the extensive resource usage happening when Chrome does this. That part of it could very well be a side effect that's compounded by the user agent shenanigans Google does with YouTube.
Goun@lemmy.ml 1 week ago
You’d be rooting for ie6 some years ago. Indeed an unpopular opinion.
Goodlucksil@lemmy.dbzer0.com 1 week ago
The problem here is that antitrust does not work correctly and google hasn’t been legally forced out of the industry due to anticompetitive tactics
DacoTaco@lemmy.world 1 week ago
Not also unpopular, but also wrong.
Often times firefox is following the css specifications in how to process it and chrome isnt. Developers then do things, see it works in chrome and leave at that, not knowing what they did is wrong and broken.On top of that logic of yours, ie10 was like the perfect browser and everyone should have kept making stuff compatible with it
lime@feddit.nu 1 week ago
that would be a more relevant opinion if google hadn’t made itself head of the web standards committee and is changing things so fast that the only party able to keep up is google.
Hupf@feddit.org 1 week ago
AHemlocksLie@lemmy.zip 1 week ago
Turns out that’s not how standards work. If all browsers implement the standard and your product doesn’t function properly on every single one of them, the problem is your product, even if it’s just a single one.
Alexstarfire@lemmy.world 1 week ago
Yes. I regularly have to either close Firefox or kill the GPU process in it so it’ll free up RAM. Worst I saw it was at 13GB.