A while back I highlighted the fact that the Gecko user-agent string was resulting in our users being served second class experiences. Facebook [1] and Google [2] were the most obvious.
These two issues were related to image assets, but the problem is worse than that. Facebook is sniffing for Chrome in order to provide Service Worker Push and Google is providing enhanced experiences across its product line for Chrome. I've been told WebCompat <https://webcompat.com> is the solution to this problem, but I'm not convinced. My two issues so far have had no sign of being fixed; simply put: why would they care? We're a small fish on mobile. I think we should be seriously considering exploring UA ambiguity (and all that that comes with <https://blogs.windows.com/msedgedev/2015/06/17/building-a-more-interoperable-web-with-microsoft-edge/>), at least on *Firefox OS, *if we are to provide the best web experience on mobile. It's hard to swallow (especially being Mozilla) but I fear the alternative is much worse. --- *Chrome:* Mozilla/5.0 (Linux; <Android Version>; <Build Tag etc.>) AppleWebKit/<WebKit Rev> (KHTML, like Gecko) Chrome/<Chrome Rev> Mobile Safari/<WebKit Rev> *FirefoxOS:* Mozilla/5.0 (Mobile; rv:<Gecko rev>) Gecko/<Gecko rev> Firefox/<Gecko rev> *Edge**:* Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136 --- [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1229026 [2] https://webcompat.com/issues/1827 *W I L S O N P A G E* Front-end Developer Firefox OS (Gaia) London Office Twitter: @wilsonpage IRC: wilsonpage
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
