Firefox Community Forum

Firefox kicks me out! My Mac works like a charme without any hardware problems. But now my favorite browser (FF) quits support. I'm amazed that a project like Mozilla does not care about sustainability. Any update in the software world must take care concerning downward compatibility - otherwise you exclude former users/customers. So why is ESR for Macos 10.9 to 10.11 not supported anymore? There are millions of Core2Duo-machines, that Mozilla sends to the trash. I'm extremely disappointed!

What do these question marks mean? Do they indicate tentatively planned releases?

Bottom line: will there be 115.22 through 115.24?

/uploads/images/2025-03-23-07-41-00-a333e6.png

I am running Windows 11, with Firefox 97.0 ("Up To Date"), but the installer for the new 115 ESR does not work.

The installer (Firefox Setup 115.18.0.esr.exe) seems to think that my system is running Windows 7 and does not proceed.

My company relies on another company for our VM using Amazon Linux 2 and installs Firefox ESR from Amazon Linux 2 extras. We have 115.18.0esr and were getting notifications at the top of Firefox saying this would stop working on 14th March. We got 128.7.0esr but it core dumped on loading even in safe mode and when creating a new profile. So downgraded and then found another coworker faced same issue so go him to also downgrade. I then went to recreate my issue get logs and screenshots to provide to my supplier but 128.7.0esr has disappeared from the amazon linux yum repo and the notification about the need to upgrade before 14th March has also gone and gone from co worker machines. I think it was needed for plugin and cert issues but I am not sure. I realise I should reach out to the supplier for them to then contact Amazon and find out what the issues are from their yum repo and see if it is anything to do with their provided vm. But has anyone got any info on the reason to upgrade from 115.18.0esr so I can add to the issue? I know it's EOL but the message was specific and came from Firefox and links which took you to info about why it was needed but it seems weird the notification has disappeared.

I'm on a Mac running OS 10.14.6. I have consistently updated, and currently have Firefox 115.20.0esr. Yesterday a tax website said my Firefox was out of date, and wanted me to update. From within Firefox I clicked to update, and it downloaded an installer. But when I installed this new update, it's the same version: 115.20.0esr.

Can you shed any light on this? Is there any reason to keep this "new" version of Firefox?

Thank you for your help!

Like probably a Lot of you I don't support the unethical So-called "Forced-obsolescence" and am not planning to "upgrade" Microsoft every 18 months or so for the next 90 years on each on Every single family Computer and give in to their Scare tactics for financial, environmental and Ethical reasons.

I am currently running Firefox "Extended Support," or ESR, I think it's called. Was wondering, If I ever **DO** decide to upgrade our bloatware Spyware operating system(s), basically if they break enough Apps like Apple Likes to do to force an upgrade, how difficult or easy would it be to Migrate from ESR to the latest regular version of Mozilla/Firefox...with all my Settings, etc. still in place?

Hi, During some tests I found that FF 115.19.0esr can still execute arbitrary JS similarly to CVE-2024-4367. I’ve checked the versions and > 115.11esr should be patched. Any payload with ‘/JS’ taken from https://github.com/luigigubello/PayloadsAllThePDFs/tree/main will do. Since this is probably important – FontMatrix is *not* working (no JS), original PoC (https://codeanlabs.com/wp-content/uploads/2024/05/poc_generalized_CVE-2024-4367.pdf) is also *not* working. I also wasn’t able to call an external script and so far haven’t found any path to exploit it beyond an alertbox. However, it still bothers me a lot and I’d like to know whether it’s the correct, expected behavior with FF+pdf.js, is it a vulnerability, or maybe my browser was somehow corrupted or is using some other mechanism that’s not within your control (my settings? about:config?).

Steps to re-create: 1. Open file in notepad 2. Add ‘/OpenAction 99 0 R’ after ‘lang’ in ‘1 0 obj section’ 3. After ‘endobj’ add ‘99 0 obj <</Type /Action /S /JavaScript /JS (app.alert\(1\);)>>’ 4. Result – alertbox popping twice

Dear Sir,

Firefox is not working with Rabby Wallet and Metamask extensions.

It does no pop-up the window to see the transaction and sign it. Firefox 134.0.1 (64-bit). Windows 10 Home.

On Metamask at least I can click on the pinned extension and see the window. However it´s not the expected behavior, because it should open the pop-up automatically. With Rabby wallet it is impossible to proceed, even clicking on the extension icon.

Please fix it.

I have just got a new laptop and installed everything in relation to Firefox onto it. I have used the Nordpass extension for a couple of years and on the old laptop this is version 5.23.13 updated 16/10/24. On visiting the add-on and extension site today there is only a legacy version 4.33 updated 2y ago which clearly no longer works. Where has it gone. Clearly I am going to ask the same question of Nord, but I hope you can help.