11–20 of 46 posts
Also saw other strange behaviours. While writing a comment, taps on the spacebar were not detected, but typing some letters also triggered the browser's Back functionality (I did not hit Backspace).
According to an analysis in the Firefox bugtracker (https://bugzilla.mozilla.org/show_bug.cgi?id=1697551) it seems like the error occured because a non-standard attribute is used in the JS code that only Chromium implements.
Looks like the changes are being rolled back though. Geniunely happy to see that as Youtube hasn't such a good track record of fully suporting browsers not based on the Chromium engine. I think performance on Firefox is still pretty bad with the new UI because of some inperformant polyfills for Shadow DOM code?
Same for me on Firefox. Bizzare.
> "Google Chrome ads started appearing next to Firefox search terms. Gmail & [Google] Docs started to experience selective performance issues and bugs on Firefox. Demo sites would falsely block Firefox as 'incompatible'," he said.
> "All of this is stuff you're allowed to do to compete, of course. But we were still a search partner, so we'd say 'hey what gives?' And every time, they'd say, 'oops. That was accidental. We'll fix it in the next push in 2 weeks.'
> "Over and over. Oops. Another accident. We'll fix it soon. We want the same things. We're on the same team. There were dozens of oopses. Hundreds maybe?"
> "I'm all for 'don't attribute to malice what can be explained by incompetence' but I don't believe Google is that incompetent. I think they were running out the clock. We lost users during every oops.
I wonder if Youtube doesn't run CI tests against other browsers than Chrome or if those test cases just aren't covered. According to an analysis in the Firefox bugtracker ( https://bugzilla.mozilla.org/show_bug.cgi?id=1697551 ) it seems like the error occured because a non-standard attribute is used in the JS code that only Chromium implements. Looks like the changes are being rolled back though. Geniunely happy to s…