8 ms·

For reference, this is being tracked by Mozilla's webcompat group in https://bugzilla.mozilla.org/show_bug.cgi?id=1131601 https://bugzilla.mozilla.org/show_bug.

• eginhard 12y ago
  And it was apparently "blocked by mistake and will be fixed very soon": http://venturebeat.com/2015/02/10/google-play-no-longer-supports-firefox-for-android-did-the-browser-war-just-get-ugly/ http://venturebeat.com/2015/02/10/google-play-no-longer-supp...
  • kapok 12y ago
    Come one, don't be naive... https://bugzilla.mozilla.org/show_bug.cgi?id=668275 https://bugzilla.mozilla.org/show_bug.cgi?id=668275 The whole point of web standards is to create a - you know - "standard" basis everybody can build upon. If your webapp doesn't work on a given recent browser (firefox latest is both recent and decent), you're doing it wrong. And Google has been doing it wrong for years (since 2011 for Gmail). Not only is it wrong in the sense that it's poorly developed, but it's also wrong in any other sense of the word (evil, bad,...). We're talking about a company that develops a web browser and that, in 2015, serves barely usable version of their services when the UA doesn't match its own. Edit (for the sake of completeness): if you don't spoof the UA of firefox mobile, you can't use gmail except for painfully reading e-mails.