InformAction Forums

Where, ex

lilmonkey wrote:It seemed to have been fixed for a while, but now the message is back in an endless loop.

"In order to operate on this tab, NoScript needs to reload it. Proceed?"

Where exactly? And with all the other extensions disabled?

Giorgio Maone wrote:Should be fixed in latest development build,
v 10.1.7.3rc1

Appears to be working normally for me now. Thanks for the quick fix, Giorgio.

Everything is back to normal for my browsing. Thank you all for your effort and the continued maintenance of a really outstanding tool... and all for free! How could it possibly be better?!

10.7.3 does the trick for me as well. No more 'reload'-loops. Thank you for the quick fixing, Giorgio!

I've got the latest RC release (10.1.7.4rc1) and I'm still having issues.
Using Firefox-57 on Linux-64.
On SOME sites if I click on the (S) I get the nice popup.
But on other sites, when I click on it I get nothing. The icon is saying (S/)39, so I know the site is asking for scripts, but I can't pop up the dialog to control it. Another tab says (S/)11 and I cannot pop that up. But another site is fully trusted, so when I click on that it DOES pop up the (one line) entry window. But then on yet another tab, I can't pop it up even though it's reporting fully trusted (S).

Guest wrote:I've got the latest RC release (10.1.7.4rc1) and I'm still having issues.
Using Firefox-57 on Linux-64.
On SOME sites if I click on the (S) I get the nice popup.
But on other sites, when I click on it I get nothing. The icon is saying (S/)39, so I know the site is asking for scripts, but I can't pop up the dialog to control it. Another tab says (S/)11 and I cannot pop that up. But another site is fully trusted, so when I click on that it DOES pop up the (one line) entry window. But then on yet another tab, I can't pop it up even though it's reporting fully trusted (S).

Why are you stuck with Firefox 57 (which is obsolete, insecure and doesn't support some APIs which are needed for full functionality and best performance of latest NoScript)?
Could you please upgrade to 59.0.1 and, if the problem persists, share your NoScript Options>Export output (by email, if you prefer)?
Thanks!

Giorgio Maone wrote: Why are you stuck with Firefox 57 (which is obsolete, insecure and doesn't support some APIs which are needed for full functionality and best performance of latest NoScript)?
Could you please upgrade to 59.0.1 and, if the problem persists, share your NoScript Options>Export output (by email, if you prefer)?
Thanks!

My desktop is still running Fedora 25 and I can't upgrade it until I'm done with my taxes (because I'm pretty sure upgrading will break vmware, which I need to run my tax software).

Besides, NoScript was working *just fine* in Firefox 57 until a few days ago. I'm happy to downgrade NoScript to the previous working version if you can point me to it. IMNSHO, an "auto update" should not cause loading a version that is known to break. If an update requires features not supported by the browser then the auto-update should not update to that version.

Thanks.

Guest wrote:

Giorgio Maone wrote: Why are you stuck with Firefox 57 (which is obsolete, insecure and doesn't support some APIs which are needed for full functionality and best performance of latest NoScript)?
Could you please upgrade to 59.0.1 and, if the problem persists, share your NoScript Options>Export output (by email, if you prefer)?
Thanks!

My desktop is still running Fedora 25 and I can't upgrade it until I'm done with my taxes (because I'm pretty sure upgrading will break vmware, which I need to run my tax software).

You can just upgrade Firefox, though

Guest wrote: Besides, NoScript was working *just fine* in Firefox 57 until a few days ago. I'm happy to downgrade NoScript to the previous working version if you can point me to it.

Likely 10.1.6.5 from https://noscript.net/feed

Guest wrote:IMNSHO, an "auto update" should not cause loading a version that is known to break.

It's not "known to break" (until now, at least), but of course unsupported versions (any version number lower than current stable, except ESR) can't be as much tested as supported ones.

Giorgio Maone wrote:

Guest wrote: My desktop is still running Fedora 25 and I can't upgrade it until I'm done with my taxes (because I'm pretty sure upgrading will break vmware, which I need to run my tax software).

You can just upgrade Firefox, though

Point me to the Fedora-25 RPM of Firefox 59 and I'll gladly install it.

Giorgio Maone wrote:

Guest wrote: Besides, NoScript was working *just fine* in Firefox 57 until a few days ago. I'm happy to downgrade NoScript to the previous working version if you can point me to it.

Likely 10.1.6.5 from https://noscript.net/feed

Thanks. That version seems to work for me. I've locked it at that version (turned off updates) for now.

Giorgio Maone wrote:

Guest wrote:IMNSHO, an "auto update" should not cause loading a version that is known to break.

It's not "known to break" (until now, at least), but of course unsupported versions (any version number lower than current stable, except ESR) can't be as much tested as supported ones.

Sure you can. Just run a few VMs that are using distributions that are only ~1 year old.

Guest wrote: Point me to the Fedora-25 RPM of Firefox 59 and I'll gladly install it.

Using a safe and supported browser version, rather than one with publicly known security bugs, trumps the inconvenience of installing a statically compiled Firefox from the official Mozilla-provided Linux tarball or "downgrading" to the ESR version IMHO. But it's just a matter of priorities, I guess.