[Unrelated] NoScipt refuses to unblock some pages

[pokeefe0001]

In the past, repeatedly clicking "Temporarily TRUSTED" would (eventually) allow access to any page I visited. In the past couple years I've fount pages that simply could not be unblocked. The same list of scripts would be displayed each time the button was clicked. "Disable restrictions for this tab" and even "Disable restrictions globally" would not allow access to the pages. Disabling the NoScript plugin in Firefox does allow access to the page.

This is very frustrating.

On such page (if the link is still valid) is
https://attcx.sjc1.qualtrics.com/jfe/fo ... _CHL=email
It's a survey page for AT&T.

[Giorgio Maone]

On such page (if the link is still valid) is
https://attcx.sjc1.qualtrics.com/jfe/fo ... _CHL=email
It's a survey page for AT&T.

This page works for me, I just had to set qualtrics.com to temp. TRUSTED.
However for actually getting the survey and not a "session expired" message I had to remove the query string:

https://attcx.sjc1.qualtrics.com/jfe/fo ... SRjrHWzTVA

I suspect you may have a broken configuration or an extensions conflict.
Could you try:

1. Use NoScript Options>Export to save your current configuration to a file and NoScript Options>Restore to reset it.
2. If #1 helps, send me the file for analysis
3. Otherwise please create a clean profile from scratch. Install only NoScript, leaving all the defaults.
   Does the problem still exist? If not, NoScript is not the culprit. Try adding back your extensions, one at a time, until you find the one that causes the issue. Then remove all the others, pairing only the suspected one with NoScript, to confirm that the remaining one is the issue.
   If the problem is solved even with all add-ons reinstalled, then the previous profile was probably corrupt. Problem solved.

Good luck and let us know.

[pokeefe0001]

Apparently the NoScript problem doesn't happen when the "You've already taken the survey" web page is displayed. I need to find another problematic page. This may take me a while. Sorry.

[pokeefe0001]

Well, I cannot remember other problematic pages. I've run into them every couple months but haven't documented them. The previous one was about 6 weeks ago, but I can't find it now. I'll start a new thread the next time that happens ... if it happens again.

[barbaz]

I'll start a new thread the next time that happens ... if it happens again.

Please only start a new thread if you are sure the reason NoScript won't unblock the next example page is not the same reason it wouldn't unblock this one.

For the next example, please open Web Console (Ctrl-Shift-K) and check for any errors while NoScript is breaking the site that do not exist when loading the site with NoScript disabled.

[pokeefe0001]

I assumed this thread would be closed due to inactivity by the time I have new information. It's likely to be weeks if not months.

[barbaz]

I assumed this thread would be closed due to inactivity

We don't do that, see Forum Rules #14.

[pokeefe0001]

I have not been able to reproduce the problem, but I run into to it only a few times a year so that means nothing. I've given up trying to remember the problematic pages. I'm not aware of doing anything that might have fixed the problem so I assume this is just a matter of bad (or good) luck. Hopefully someone else will run into it.

[pokeefe0001]

OK. I found a somewhat problematic page. This page will not load if NoScript is active. It will load with "Disable restrictions for this tab".
(I'm still waiting to find a more problematic page that requires NoSctipt to be removed from the browser.)

https://click.info.geappliances.com/?qs ... a45e1a84a0

This is a GE Appliances order status page. With NoScript active it starts with 5 blocked items - 4 scripts, 1 font. Setting temporarily trusted reduces that to 1 blocked item - a font. (When I first tried accessing the page setting temporarily trusted took the blocked count down to 2; I had to manually reload the page and set temporarily trusted 2 more times before I got it down to just the blocked font. I have no idea what a blocked font is, but disabling restriction for this tab apparently allows the font to be used.

I took several screen shots to document this, but I don't see that inserting images or attaching files is allowed.

[barbaz]

^ Sorry but we can't test that page as it requires your personal info. Since I don't have your login for that site, it thinks I'm a bot - and redirects me to a page which requires either logging in as you or proving that this is my order & that I'm not a robot.

Not sure if related or not, but are you able to upgrade to a newer version of Firefox (at least latest 115 ESR)? Some Firefox issues affecting NoScript have been fixed since 102.x.

I took several screen shots to document this, but I don't see that inserting images or attaching files is allowed.

You can upload them to an external site (either a dedicated image hosting site, or something like Google Drive / Dropbox / Onedrive if you have) and post the link here.

[pokeefe0001]

^ Sorry but we can't test that page as it requires your personal info. Since I don't have your login for that site, it thinks I'm a bot - and redirects me to a page which requires either logging in as you or proving that this is my order & that I'm not a robot.

If you got to the page requiring logging, etc. you didn't experience the problem I had.

Not sure if related or not, but are you able to upgrade to a newer version of Firefox (at least latest 115 ESR)? Some Firefox issues affecting NoScript have been fixed since 102.x.

Ah. You're right. I tried it on another computer - a test PC - that has FF 113 and didn't experience the problem. Sorry to waste your time. I'll update to FF 113 on my "production" PC and put 115 on my test PC. (Maybe 115.0. The 115 ESR releases are far too recent for me to consider.)

[barbaz]

I tried it on another computer - a test PC - that has FF 113 and didn't experience the problem. Sorry to waste your time.

Thanks for reporting back.

(Maybe 115.0. The 115 ESR releases are far too recent for me to consider.)

off-topic: While I believe the issues alluded to were indeed fixed in either Firefox 113 or Firefox 114, we generally recommend avoiding using outdated browser versions when possible, because they have publicly known security vulnerabilities. The purpose of the ESR channel is to provide fixes for security vulnerabilities without requiring being on "far too recent" releases.

(BTW, just to be clear, the "far too recent" concern is very understandable to me - in fact my signature is sort of related to this concern )