Page 1 of 1

url shortcuts

Posted: Fri Dec 02, 2022 4:19 am
by W7810
Firefox 107.0.0 and 107.0.1
noscript 11.4.13
Problem exists on Win7 and Win11.
Problem does not exist in Edge, on either Win7 or Win11.

When opening Firefox via a shortcut then allowing temporary permissions with noscript, the settings are applied but not executed after reloading page. Issue still exist in new profile with only noscript installed.
If Firefox is first opened then go to url via shortcut, things work as expected.
I think problem began with Firefox 107 update, but I could not say for sure.
Sample page where it happens https://tennislink.usta.com

Re: url shortcuts

Posted: Fri Dec 02, 2022 5:25 pm
by therube
Explain further?

So this is a "desktop" shortcut?
And you click that, & https://tennislink.usta.com/ loads.

You (temporarily) Allow usta.com.

The page refreshes, then what does or does not happen?


Does the same occur if you start FF from a command line?
C:\> firefox.exe https://tennislink.usta.com/
Then Allow usta.com...

(If I test like that, & not that I know what to expect, particularly, all looks to be OK.)

Re: url shortcuts

Posted: Sat Dec 03, 2022 12:44 am
by Guest
Yes, an url shortcut in the file system.
If firefox is not running and is opened by an url shortcut, scripts given temporary permissions do not run when page is reloaded.
If, however, firefox is already running when url shortcut is opened, scripts with temporary permissions run when page is reloaded.
This happens with approx 80% of pages I open via shortcut.

Re: url shortcuts

Posted: Sat Dec 03, 2022 12:54 am
by Guest
After trying everything I knew to do, I uninstalled Firefox and reinstalled, and things are working as expected now.

Re: url shortcuts

Posted: Sat Dec 03, 2022 12:58 am
by Guest
Sorry, I opened shortcut with firefox already running. So nothing has changed.

Re: url shortcuts

Posted: Sat Dec 03, 2022 3:37 pm
by barbaz
W7810 wrote: Fri Dec 02, 2022 4:19 am I think problem began with Firefox 107 update, but I could not say for sure.
So as a test, if you downgrade to Firefox 106 (or whatever version you were using before) does the problem stop?

https://ftp.mozilla.org/pub/firefox/releases/106.0.5/

Using an existing profile with an older Firefox version will involve starting Firefox with --allow-downgrade command-line option. I don't know whether that needs to be used only once or if it always needs to be used.

Re: url shortcuts

Posted: Sun Dec 04, 2022 12:30 am
by Guest
I have tried multiple combinations of previous versions of Firefox and noscript in a fresh virtual machine, going back to Firefox 99 and noscript 11.3.7, and have the same problem in every scenario. Deleting all Mozilla AppData folders after uninstalling each time.
I don't know what's going on and I'm tired of fooling with it. Will just have to open firefox before opening shortcut urls, or use Edge.

Re: url shortcuts

Posted: Sun Dec 04, 2022 6:29 pm
by Guest
After watching Dev Tools console logging, it appears Content Security Policy is at the root of this behavior.
If Firefox is NOT up and running and a shortcut url from the file system opens Firefox, is Firefox setting the Content Security Policy for the page in such a way that some same-origin policy is now preventing the running of the temporarily allowed scripts by NoScript?
Not all url shortcuts behave this way, just some, and since it was just this week I pinpointed the problem I havent had time to recognize any patterns. I do not experience this behavior with Edge.
Again, if Firefox is already up and running and a shortcut url from the file system is opened, temporarily allowed scripts by NoScript run after page reload just fine.
This is where I have to bail out, because I certainly don't have the knowledge and skill to do anything more.
Perhaps someone that does know what they are doing might have some time to burn and look into it.

Re: url shortcuts

Posted: Mon Dec 05, 2022 9:55 am
by Giorgio Maone
I've managed to consistently reproduce it in a Windows 10 VM with Firefox ESR 102, but I could not figure out yet what's going on (it seems a weird caching effect which eludes any observability from devtools / debugger).

Still investigating, thanks...