Hacker News new | ask | show | jobs
by Santosh83 3187 days ago
Seriously, when we talk so much about the Web's portability, why is a major feature from a major website not even working on identically on the two biggest browsers? Since it's Facebook we can't accuse them of browser favouritism as they're browser neutral. I wonder what APIs are missing from Firefox that makes FB Live Video broken?
1 comments
Manishearth 3187 days ago
> Since it's Facebook we can't accuse them of browser favouritism as they're browser neutral

Favoritism isn't the only reason for these things. What often happens is that the website devs all use one browser and nobody tests it.

It's not like Google wants their sites to be broken on other browsers either (I presume), it's just that many teams at Google aren't bothered.

IIRC Firefox has the same WebRTC APIs as Chrome, so this might be reliance on browser-specific nonstandard behavior.

(Or it might not. It's worth looking into, but I can't because it seems like you need to ask for an FB live invite to investigate)

Edit: Figured out how to do it. Seems to work fine in Firefox Nightly.

link
pferde 3187 days ago
> Favoritism isn't the only reason for these things. What often happens is that the website devs all use one browser and nobody tests it.

That is exactly the point the GP post makes. These things are supposed to be standardized and the standards well described, so basic things should work everywhere without any testing. But somehow for web, it is acceptable and accepted as status quo, even after years and years of smashing our heads against the wall of nonstandard, browser-specific features.

link
Manishearth 3187 days ago
Yeah. Well, it's not just "features", it's also stuff like minor differences that the spec allows for (the spec doesn't spec everything). For example, assuming the order of elements in the indexed getter of getComputedValues().

There are also cases like where Google's U2F library doesn't work with Firefox's U2F implementation because Firefox's window.u2f is immutable, as a newer (IIRC draft) spec dictates, whereas it isn't in Chrome, and the library does `var u2f=u2f||{}` which errors in Firefox.

link