> Chrome by pretending that Chrome-only APIs are essential and standard web apis

Reminds me of the days when all the corporate coders thought the IE apis were the only ones worth using.

So if you accessed $megacorp website on a non-IE browser it was your fault for not using IE and not their fault for failing interop.

I noticed how they've marked the features that only Chrome supports (e.g. installation) but not the feature that only Firefox supports (orientation).

(tbh I don't know if the list is simply Chrome-centric or if there's a good reason behind, but it struck me as interesting)

yeah I'm using mobile Firefox and it has an awfully high overlap with Safari. Almost like a bunch of the stuff Chrome supports isn't actually a standard at all yet...