Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoScript causes RSSpreview extension to fail since upgrading to Firefox 126 #356

Open
matthewkogan opened this issue May 21, 2024 · 7 comments

Comments

@matthewkogan
Copy link

aureliendavid/rsspreview#85
These worked fine together until upgrading to Firefox 126.0 last week.

@MarkusGasser2
Copy link

Exactly the same problem here: From 126 onwards, an RSS feed is no longer displayed correctly, or the display is empty. With the old Firefox versions everything was still ok. There must have been a change in Firefox.

@matthewkogan
Copy link
Author

Thanks. I've reported https://bugzilla.mozilla.org/show_bug.cgi?id=1899786 now.

@matthewkogan
Copy link
Author

For now it is possible to work around the problem by setting the Firefox preference network.decompression_off_mainthread to false in about:config.

@MarkusGasser2
Copy link

Thank you, yes, everything is ok now.
It is a real change in Firefox 126.

@jesup
Copy link

jesup commented Jun 27, 2024

Decompressing Off MainThread shouldn't change anything, except it will change timings and perhaps orders of when things occur, since decompression is no longer synchronous. From a Web Standards perspective, this shouldn't matter at all.
I suspect the timing changes combined with interactions between NoScript and RSSPreview are triggering some race conditions in the extensions. What, I'm not sure, and it would be hard for me to debug since I know little about them. (I wrote the Decompression OffMainThread patch).
If you can get more details on what happens (perhaps a full networking log via about:logging), perhaps I can help tell you where the timing change might be, but I'm not sure that would tell you more than your own debugging would

@MarkusGasser2
Copy link

Good evening.
I have found that it is not necessary to switch off network.decompression. it is sufficient to change the minimum size to 4000.

network.decompression_off_mainthread_min_size = 4000

@matthewkogan
Copy link
Author

The preference to set to work around this has been renamed in Firefox 128 to network.decompression_off_mainthread2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants