The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.
You can subscribe to this community from any Kbin or Lemmy instance:
Related
While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.
Always be civil and respectful
Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity.
Don't be a bigot
No form of bigotry will be tolerated.
Don't post security compromising suggestions
If you do, include an obvious and clear warning.
Don't post conspiracy theories
Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources.
Don't accuse others of shilling
Send honest concerns to the moderators and/or admins, and we will investigate.
Do not remove your help posts after they receive replies
Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.
I have 3 Windows x64 machines:
Firefox 115 running flawlessly on all of them. No issues, fast and smooth. Same as previous versions.
Kind of a big update... this is the last version of Firefox for Windows 7 and Windows 8, along with macOS 10.12, 10.13, and 10.14. I know this is forcing family members to finally upgrade their (mac) OS.
More big updates:
Pretty sure that last feature is what finally fixes the Reddit Fancy Pants editor in Firefox... exactly when Reddit is destroying itself.
This might help WhatsApp web run in private browsing, among other sites.
The most impactful thing is definitely going to be OS compatibility... this is going to be the last version of Firefox for a long time for a lot of people.
Can someone explain the Intel h264 decoding thing?
I've had h264 decode on GPU working with VAAPI since forever. This seems to be telling me about a feature I already had years ago?
i have a feeling there is something horribly wrong with 115.
firefox has been lagging and using too much ram. 114 was the best patch in history but now its back to the same old struggling firefox. or worse.
If you want to find the bug, you can run a mozregression to find what broke it (using 114 as your last known good release and 115 as your bad release).
Please reach out if you need help with this.
You can use your profile to test this pretty easily.
Been enjoying Edge for a year, but always appreciated FF for it being it's own thing. Worth a shot?
I genuinely think the web has become horrible enough where the browser you use does not really matter from the technical perspective.
It does, however, incredibly important to have more than 1 engine competing, as currently Firefox is the only mainstream browser not built on chromium/google.
I use edge at work (nothing else available), Firefox everywhere else.
It would be nice if more add-ons were supported on mobile, desktop is great.
Certainly. It's really important to have as many people as possible using a different browser engine (Gecko) in this Chromium-dominated world.
And ... uBlock Origin works the best on Firefox (https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox).
Firefox was great, went to shit for a couple of years, and is now back to being great again. I've heard it's much easier on memory as well.
It's one of the few non-chromium browsers left, so you should definitely try it because Google is trying to make their own standards with chromium.
It's literally the only non-chromium browser left other than Safari. That's why it is critically important that Firefox maintain a presence
edit: culprit found: dashlane extension for firefox causing latency and high use of resources.. dashlane claims they are waiting on mozilla to review their patch submitted 3 weeks ago:
I am not seeing any patch submitted to Mozilla by Dashlane on this bug which looks like it is at an investigation phase, is that in a separate bug?