[deleted]
Google Play Store: Browsing with Firefox is no longer supported on Android
191–200 of 242 posts
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#192Doesn't appear to be related to Firefox. I tried it from Chrome on my desktop (with dev-tools emulating a Nexus 5). See screenshot. Looks like if you're on a mobile device at all they want you to use the app instead of your browser.
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#193have you seen firebox for android? it's years ahead of chrome.
you can have extensions to begin with. from ad blockers to stylish, which let people with poor vision actually use the browser.
also it allows you to disable all sort of asinine tracking that is forced in chrome.
expect Google to play a Microsoft on Mozilla harder and harder now.
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#194This is a dangerous slope. And I'm sad seeing many of the arguments here - a wild guess is that they've been made by people who weren't here (or have forgotten) the Microsoft/IE story. Soon it will become: "Why would they invest resources? Firefox is a niche browser, the return on investment is not justified". After all, Firefox's market share is dwindling. I really hope we're not slowly being boiled like the proverb…
i disagree. i think what we all must do is tell everyone exactly that.
"don't use Google play store, it's like ie6. use fdroid and be happy". and then we all drop support to it, just like we dropped support to ie6 and it's bullying tactics, even though we own ajax to it, there's so much abuse one can take.
do your part for free software. but yeah, i know that building your startup on top of a free software stack means nothing when you can give in to a walked garden and sell your closed source app for 99c
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#195time to switch to f-droid, as an open-source app store.
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#196have you seen firebox for android? it's years ahead of chrome. you can have extensions to begin with. from ad blockers to stylish, which let people with poor vision actually use the browser. also it allows you to disable all sort of asinine tracking that is forced in chrome. expect Google to play a Microsoft on Mozilla harder and harder now.
Firefox for Android also has nicer default fonts and MathJax works! (MathJax on Chrome for Android renders with parts of formulas overlapping other parts and overlapping surrounding text.)
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#197Earlier quoted context omitted.
Months later, inbox.google.com still requires Chrome, despite it working perfectly well in Safari when spoofing the UA, and claims that it was held back by "performance issues on some animations", and while I've had a few occasional bugs running it in Firefox, it seemed to be altogether quite fine. Anyway I stopped using the thing a month ago because I simply dropped Chrome†. † slowly becoming too much ChromeOS-and-w…
I'd like to take a moment to focus on that last point: Chrome has become the memory hog that caused us all to leave firefox but for the much more egregious reason of trying to be something it's not. Now when I close chrome it wants to stay open like an over eager registry cleaner that hopes to hide behind the always on functionality and thus obscure that fact that it's done nothing, only Chrome's reason is the slight…
For me, Chrome uses half the memory of Firefox for the same number of tabs. If you're having memory issues with a browser, your problem is almost certainly extensions - the #1 culprit being AdBlock [Plus]. Give µBlock a try. (The reason why my Firefox uses more memory per tab is in fact almost certainly extensions.)
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#198Earlier quoted context omitted.
There is potentially a critical difference here. The "We don't support IE" mini-movement was a reaction to Microsoft's refusal to use the web standards that every other major browser supported. In this case, it appears to me (admittedly without research) that Google's motivations must be different, and two possibilities spring to mind: (1) Google doesn't like the competition from Firefox or (2) the Play store uses no…
Not really. Since IE10 a lot of the standards argument has been bunk and I've run into a lot of sites lately that tell me, "Oh this html5 feature is only on Chrome, so use that" when I use Firefox. Or if I'm using IE11 for work, suddenly I hit a site that either tells me to get lost or warns me that I'll get a better experience with Chrome. The problem is we let web culture degenerate into a "my browser or the highwa…
> Google knows this and is using this to its advantage with its long-range plan to lock people onto its proprietary Android-based services. Now here's another reason to not use Firefox and to stick with Chrome.
Based on your argument, I think it's time for the opposite.. stick with Firefox
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#199Nobody uses firefox anymore anyway so who cares?
On Android I would probably use Chrome if it weren't for a particular bug. I mean Chrome comes with my tablet and cannot be removed, so I'll use it unless I can't. But MathJax doesn't work in Chrome for Android and works just fine in Firefox for Android (it works in the desktop versions of both browsers).
If faced with a choice between giving up a browser or giving mathematics, I'll choose the browser every time! :)
Re: Google Play Store: Browsing with Firefox is no longer supported on Android
#200Earlier quoted context omitted.
“Anyone who slaps a ‘this page is best viewed with Browser X’ label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network.” – Tim Berners-Lee (in Technology Review, July 1996)
It's browser vendors that are bearing the torch of interoperability and standards compliance. Unfortunately, most vendors are companies with their own agenda. To add to that, all companies and people interpret standards differently. Given this, it's no wonder we don't see consistent api implementation and behaviors between browsers. The aftermath of all of this falls on the developer's shoulders, which is why so many…
"When you start using a seemingly mature HTML5 api, and find that it doesn't work as expected in all browsers, what recourse does one have?"
File bugs. Chromium and Firefox are not black boxes.