Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多
Solved 封存

ChatGPT not working after new browser update

pankewycz

After being prompted to update the browser this morning, and after I updated it, I can no longer use ChatGPT. Chat GPT will open, but it's unresponsive, can't log in, the arrow button to submit an inquiry doesn't work, and none of the other features of ChatGPT are working

After being prompted to update the browser this morning, and after I updated it, I can no longer use ChatGPT. Chat GPT will open, but it's unresponsive, can't log in, the arrow button to submit an inquiry doesn't work, and none of the other features of ChatGPT are working
從原來的回覆中察看解決方案

選擇的解決方法

Hi all,

An update (v147.0.1) has been released to set network.http.dictionaries.enable to false for all users, while the team is working on a proper fix for the feature. Sorry for the inconvenience, and thank you TyDraniu for sharing the workaround!

所有回覆 (7)

Try to go to about:config and set network.http.dictionaries.enable to false, then report back if it started working.

Pardon my ignorance, but I don't know how to "go" to about:config. Please help me understand how to go there. Thanks :)

Type about:config in the address bar and press Enter, then find that preference using Search field. Then switch it to false using a button. After that, restart the browser.

It worked, thanks so much!

But I'm curious, what did that solution do exactly? I have almost zero knowledge of computers, but want to know how your fix fixed things for me.

That pref turns on/off a new feature - HTTP Compression Dictionary support - that has been introduced in version 147. It looks like it doesn't work well with that website.

Awesome. You rock! Take care :)

選擇的解決方法

Hi all,

An update (v147.0.1) has been released to set network.http.dictionaries.enable to false for all users, while the team is working on a proper fix for the feature. Sorry for the inconvenience, and thank you TyDraniu for sharing the workaround!