InformAction Forums

sb5k wrote: ↑Wed Sep 04, 2024 1:38 am Is there a way to tell NoScript NOT to sync?

I don't think there is a NoScript setting for that. Some people were able to work around the issue by disabling syncing of all add-ons' data.

Are you using Firefox Sync? This is known to happen with Firefox Sync in some cases. Not sure if anyone ever solved it though

If you can reproduce the issue in a new profile by completely quitting Firefox and copying files from your main profile, viewtopic.php?p=104118#p104118 has some ideas you could use to troubleshoot and ferret out the culprit

Giorgio Maone wrote: ↑Sat Aug 24, 2024 5:59 pm

barbaz wrote: ↑Sat Aug 24, 2024 3:36 pm Does the "lazy load" capability apply to the document URL (like "unrestricted CSS" does)?

The former: it's a capability of the document triggering the load.

Awesome Added to the sticky.

Nice, thank you Giorgio!

Does the "lazy load" capability apply to the document URL (like "unrestricted CSS" does)? Or does it apply to destination URL of the lazy-loaded resource?

Was about to update NoScript to 11.4.35rc2, but decided not to upon seeing this - v 11.4.35rc2 ============================================================ [...] x Forcibly neutralize lazy loading attributes when scripting is disabled Forcing this change will negatively impact using some websites wi...

Fixed in latest development build 11.4.35rc1?

In my experience those aren't random. When you figure out which specific cloudfront.net domains imdb needs, you can set them CUSTOM with contextual permission for imdb (click the "ANY SITE" drop-down in the NoScript popup). Then when reviewing NoScript Options > Per-site Permissions, knowi...

STR: Open the "General" tab in the settings, check the box "Temporarily set top-level sites to TRUSTED". Open the site http://example.com/ (or any other if TRUSTED is not selected for it in the "Per site Permissions" tab). Click on the NS icon in the panel — the "...

Do you have another extension that maybe blocking the requests NoScript causes as an internal implementation detail? NoScript intercepts and blocks these requests before they're actually sent, but if another extension blocks them before NoScript can see them, weirdness like this can result. If using...

If you go Tools > Add-ons and Themes, and disable all extensions other than NoScript, does the issue still occur?

Did the problem start at the same time as you upgraded Firefox to a newer version?

When this issue occurs, do you see anything related in the Browser Console? (Ctrl-Shift-J) (if you don't know what's related, turn off CSS warnings and post everything else you see) Before running into the issue and checking for Browser Console messages, make sure the Browser Console is set to "...

I couldn't find how to mark this topic as resolved. It isn't resolved until either fixing the incompatibility with FF 78 or increasing NoScript's minimum Firefox version requirement to what's actually compatible/supported. If Giorgio doesn't see this thread, this might be worth an issue at NSCL iss...

IMHO NS 11.4.34 is not at fault. As long as NoScript declares compatibility with FF 78, any incompatibility with FF 78 is a NoScript bug. So I suppose I just need to remove NS from FF and then download the version that's safe, right? No. Don't remove NoScript as this may delete some of your NoScrip...

4td8s wrote: ↑Fri Aug 09, 2024 5:06 pm maybe use the much older 10.1.7.3 version for FireFox 78.x

Why? What's broken with NoScript 11.4.31 on Firefox 78.15esr?