251–260 of 395 posts
Earlier quoted context omitted.
It's literally supposed to be the new Firefox for Android. So the 'Firefox' umbrella seems reasonable?
Reasonable for the product, which is not the same as the organization. At Microsoft they make Windows. At Mozilla they make Firefox.
I'm referring to the bugs that cause extreme CPU usage and as a consequence extreme heating and battery usage, mainly on macbooks with retina screens set to "more space" resolution.
I work in a whole building full of developers where every single mac user has stopped using firefox due to this issue, yet there seems to be a deep disconnection between how prevalent the issue is and the priority it seems to be assigned.
I hope I'm not coming off as an ass here, I'm just sad that I've had to move away from firefox and to see all my coworkers also moving to chrome.
Earlier quoted context omitted.
(minimum viable product) Isn't it strange that the big flash announcement comes before MVP?
The big flash announcement is to get early adopters for testing. There's no reason to delay testing until the MVP is ready, as long as testers remain aware that Firefox Preview is a preview that shouldn't be expected to already have all features implemented.
advertising is an abomination that destroys the utility of the internet
and so there's no fair comparison.
Why does the link to the preview release go through a tracking site and not directly to the Play Store?
I'm aware that I'm reaching a Cartago-delenda-est situation here, but since I see some mozilla devs here I must ask: Is there any news about the deal breaker bugs that are still keeping thousands of people from moving to firefox on OSX? I'm referring to the bugs that cause extreme CPU usage and as a consequence extreme heating and battery usage, mainly on macbooks with retina screens set to "more space" resolution. I…
Add extensions support and disable telemetry/remote-control by default (pushing updates where you control the code is remote control, don't even try to argue against that one).
> disable telemetry/remote-control by default (pushing updates where you control the code is remote control, don't even try to argue against that one). So they shouldn't put updates on the Play Store?
I can't use Play because I've got no GApps in my phone, so I can't try their app unless I find a copy "somewhere" and convince myself it hasn't been poisoned. I got a reasonably up-to-date Firefox through APKPure, and later on after watching that 35C3 talk [1], I unzipped and grepped all those saved .apks to find the APKPure app itself and Firefox and LingoDeer had the same traces of Facebook's SDK in them. So that's off the table, huh? The ones that I saved from older phones after having gottten them through Play were all fine, but I can't update those without grabbing another phone and letting Google ... play in it.
Just the other day I asked the Waterfox team for an apk and an md5sum, for the same reason-- though I'd settle for the md5sum alone! But Mozilla has resources WF can barely dream of, and it apparently intends to be a champion for privacy, so this is kinda sad.
To any Mozilla/Firefox developer reading this. I try to convert people to Firefox. The number one reason people switch, by far, is because mobile has add on support. So I say to push this front and center in marketing (I know this is a preview). People are reluctant to switch their desktop browser because chrome pretty much has the same features. But it they switch their mobile browsers they also switch their desktop…
We're certainly aware of how significant ad blocking extensions are. This release required a great quantity of features with only a six month timeline until now. We already support a very limited set of the WebExtensions API to offer features like Reader Mode. Rest assured that more features will land in the coming months. If you're a developer and you want to help us, our Github site is at this link. We mark easier…
A usable night mode e.g. invert the topbar icons and change the white screen you see before the page loads combined with an existing dark theme would be an easy feature to implement and would put it miles ahead of other mobile browsers too. I presently have to use Swift for Samsung to overlay a proper black theme (with white icons etc), but still get bright white when loading pages.
I'm aware that I'm reaching a Cartago-delenda-est situation here, but since I see some mozilla devs here I must ask: Is there any news about the deal breaker bugs that are still keeping thousands of people from moving to firefox on OSX? I'm referring to the bugs that cause extreme CPU usage and as a consequence extreme heating and battery usage, mainly on macbooks with retina screens set to "more space" resolution. I…
For me adding "Auto Tab Disard" [1] (a Firefox equivalent of The Great Suspender for Chrome) has reduced my FF memory/CPU footprint by 10x. It defaults to 10 minutes which is usually long enough where you've mostly forgotten about the tab, then it will refresh when you focus on it. A feature fortunately becoming native to FF. I don't seem to have the previous performance issues anymore but I'll be looking for it now.
[1] https://addons.mozilla.org/en-CA/firefox/addon/auto-tab-disc...