Re:YouTube change served lower-quality video to Firefox 43 f...
by debaserab2 on Monday January 11, 2016 @12:19AM
(#10878976)
Another school of thought is that it doesn't matter if it's the responsibility of the browser because the customer perception will be that your website does not work for them.
If a mechanism exists to prevent your customer from perceiving this, as a business the smart decision is going to be to use it.
Re:YouTube change served lower-quality video to Firefox 43 f...
by pmontra on Monday January 11, 2016 @04:34AM
(#10879798)
Partly true, because if they try with another browser and get a good result they'll blame the browser and not the website. In this case, they'll probably say the the new Firefox broke YouTube. See one of the comments at www.pclinuxos.com/forum/index.php?topic=135323.0
"i'm getting a lot of corrupt unsupported browser when accessing video on other sites, so i'm using chrome. i can't figure out if it's flash or firefox but i'm tired of opening the hood, i'm done with FF for now"
Most of them looked for a workaround and spoofed the user agent, but they are the kind of people that fiddle with settings. Normal users probably either don't notice or change browser.
Re:YouTube change served lower-quality video to Firefox 43 f...
by spoondan on Sunday January 10, 2016 @10:15PM
(#10878561)
YouTube's compatibility hacks are against buggy versions of browsers. Regardless of whether a bug is eventually fixed, once it is released, there is some segment of the user base that has it. If that segment is large enough, and the bug easy enough to hack around, then YouTube will provide a workaround rather than lose revenue.
Re:YouTube change served lower-quality video to Firefox 43 f...
by derefr on Sunday January 10, 2016 @11:31PM
(#10878817)
Sounds like the ultimate solution here is to just give browsers a killswitch, so they'll eventually just stop working if you don't keep them up-to-date. (I'm not sure whether I'm joking.)
Re:YouTube change served lower-quality video to Firefox 43 f...
by timothya on Sunday January 10, 2016 @10:25PM
(#10878597)
While you're right that it's up to the browser to fix, that can be a very time consuming process (especially for something as tricky as video). YouTube doesn't want to wait around for browser vendors to fix things, so they work around it themselves (just like happened in the opposite direction for this bug).
Finding workarounds for browser bugs is a common theme for the work that web developers do. Yes, browser vendors should fix the bugs, but in the meantime, there's no reason to have a bad user experience.
Edit: Not saying that's always correct, but there does seem to be a tension between: "make sure your code can work well, even in a bad environment" and "don't mask bugs, instead fix them where it makes the most sense to do so" (in this case: in the dozens of browsers instead of in millions of websites).