Updated to Firefox 115.15esr - ChatGPT and DALL-E NO LONGER WORK!

[SWDFX]

I recently updated to Firefox 115.15esr and no I can no longer access my ChatGPT or DALL-E that I have been using in Firefox for the last year. This is a serious problem as I am in the middle of a project and am now dead in the water. Why is this happening and is there a fix or when will I see a fix? See many complaints about this!

Upgrading to a new machine in a few weeks (currently on a MAC running OS X 10.14) BUT I am completely screwed at the moment and I have a deliverable in the next few days!

PLEASE HELP!!!!!

Diane W.

[vegman]

I'm having the exact same problem with 115.15 esr. I'm getting ready to dump FF if they can't fix this glitch soon!  https://chatgpt.com/ does not work with 115.15 esr !!! All I get is the chat bar at the bottom of the page with no way to submit a query.

[Roli0810]

It happened to me too

[Erf]

me too!

interactive elements don't work!

[tlh24]

Same here -- just stopped working, even after clearing the cache and cookies. 

[vegman]

Again, I am using FF version 115.15 esr with Win7 Pro.

Looks like there are a couple of errors occurring related to the Content-Security-Policy and Intl.Segmenter in Firefox.  Hope they fix this soon !!!

Here's the "Console" Data for ChatGPT.com:

Content-Security-Policy: Couldn’t process unknown directive ‘report-to’ chatgpt.com

Uncaught TypeError: Intl.Segmenter is not a constructor

    GTe https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160

    Ur https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160

    <anonymous> https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160

n0xnu42ro5xj12e5.js:160:15904

    GTe https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160

    Ur https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160

    <anonymous> https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160

Source map error: Error: request failed with status 404 Resource URL: https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js Source Map URL: n0xnu42ro5xj12e5.js.map

[Rafayelus]

Same issue here 😞 works on other browsers, error:

Uncaught TypeError: Intl.Segmenter is not a constructor GTe https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160 Ur https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160 https://cdn.oaistatic.com/assets/n0xnu42ro5xj12e5.js:160

[Agentvirtuel]

Hello

A subject https://www.reddit.com/r/firefox/comments/1flx8qw/hey_guys_i_cant_access_chatgpt_in_firefox

[vegman · Accepted solution]

Thanks, this workaround is just what I needed...worked perfectly:

This script is a Tampermonkey user script, and it’s meant to be added via a userscript manager like Tampermonkey or Greasemonkey. These extensions allow you to run custom scripts on specific websites. Here's how you can set it up in Firefox: (PS:  I used Tampermonkey not Greasemonkey)

Steps to Install the Script in Firefox:

1. Install Tampermonkey Extension:

   • Go to the Tampermonkey page on Mozilla Add-ons.
   • Click on Add to Firefox to install the extension.

2. Open Tampermonkey Dashboard:

   • Once Tampermonkey is installed, you’ll see its icon (a black square with eyes) in the toolbar.
   • Click on the icon and select Dashboard.

3. Create a New Script:

   • In the Tampermonkey dashboard, click on the + (Create a new script) button.
   • This will open the script editor.

4. Paste the Script: 

   • Remove the default text in the script editor.
   • Paste the following javascript...
     
     
   // ==UserScript==

   // @name Intl.Segmenter Polyfill for ChatGPT
   // @namespace http://tampermonkey.net/
   // @version 0.2
   // @description Fix missing Intl.Segmenter in Firefox ESR
   // @match chatgpt.com
   // @grant none
   // @run-at document-start
   // ==/UserScript==

   (function() {
   'use strict';
   if (typeof Intl.Segmenter === 'undefined') {
   Intl.Segmenter = function() {
   return {
   segment: (input) => [{segment: input || 'fallback'}]
   };
   };
   }
   })();

   
   5. Save the Script:

   • After pasting the script, click the File menu (top-left) and choose Save.
   • The script is now active and should run on chatgpt.com
     
     Good luck to everyone who uses this, and thanks again to Agentvirtuel for pointing us in the right direction !!!

[SWDFX]

THANK YOU SO MUCH!!! It worked like a champ and now I can finish my presentation!

[vegman]

You're very welcome, glad it worked for you too!

[calanger]

I'm having the same problem - ChatGPT doesn't work with 115.15.0esr, works fine with Chrome.

[vegman]

Please see the fix posted above!

[Dupliworks]

ChatGPT hasn't worked at all with Firefox 115.15esr at all for several days now. Either chatGPT page will load partially and not actually work, let you log in , or do anything, or it gives an outright 404 page for a little while then goes back to no working at all.

All of the clearing cache and stuff makes no difference, and other browsers aren't having this problem.

Is Firefox even working on this ?  It's day 3 or 4 now...

[vegman]

Please see the fix posted above.

[Dupliworks]

Hi Vegman. While I do appreciate your workaround to get Firefox working, I'm not interested in having to use 3rd party add-ons and scripts to get Firefox working out of the box again. 

Firefox needs to fix this. I'm surprised that they aren't even mentioning it yet.

[Mad_Max]

No FF does not need it. Because Mozilla already "fixed" it (actually it is not a bug fix, but addition of support for a brand new feature). It works "out of the box" in Firefox starting from version 125 and later(released more than a year ago). And if YOU personally need/want to use an outdated 115 esr version (there's nothing wrong with that, but it has its drawbacks!) then you'll have to use such "workarounds" to make everything work fine.

And for Firefox 115 ESR new features like this have not been added for a long time and will no longer be added - only the fix of critical security issues.

P.S.

The ones who need to correct their behavior are the illiterate site owners, who continue to cram all the latest fancy web features onto their sites and even mark them as "mandatory" "just in case" Despite the fact that they are not actually needed or even used at all.

This "workaround" works (not only with Chat GPT, but also with many other sites - i have tested it this few other) only because they require new features as MANDATORY, but in fact they are NOT used at all. The script above simply inserts a "dummy" (stub) instead of requested feature and sites work again fine.

[Agentvirtuel]

Hello

Firefox Release Calendar
https://whattrainisitnow.com/calendar

If you wish, you can also contact https://bugzilla.mozilla.org
https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox
https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ChatGPT you can sort

[vegman]

Thanks Agentvirtuel. I reported the bug in FF Bugzilla. I suggest other users due the same to get their attention and hopefully fix the issue by the next release!