noscript issues
Moderator: Moderators for English X Forum
noscript issues
Is anyone else having the same problem with the new version of noscript in Firefox as me.
I go to a website, select to allow all the components, refresh the page (both within the app and via the browser, the outcome is the same), but when I go bask, for lots of sites the scripts are once again disabled.
This is notably occurring on sites I buy things from, but not all such sites.
And not all sites I go too either. Not here for instance, but on Audible, which is an Amazon company, on Whittards, on Apple, Paypal, which I am starting to use more now.
It's inconsistent, sometimes it happens, sometimes not. It's irritating. I'm wondering if it's because I'm using a mac, or whether other people are having the same problems.
I go to a website, select to allow all the components, refresh the page (both within the app and via the browser, the outcome is the same), but when I go bask, for lots of sites the scripts are once again disabled.
This is notably occurring on sites I buy things from, but not all such sites.
And not all sites I go too either. Not here for instance, but on Audible, which is an Amazon company, on Whittards, on Apple, Paypal, which I am starting to use more now.
It's inconsistent, sometimes it happens, sometimes not. It's irritating. I'm wondering if it's because I'm using a mac, or whether other people are having the same problems.
If an injury has to be done to a man it should be so severe that his vengeance need not be feared. ... Niccolò Machiavelli
I've seen this issue. It has to have something to do with the new scripting/whatever format, since that was never an issue before.
This doesn't seem to happen for sites I've added to my "list" of exceptions, though. It only happens when I'm configuring permissions on the fly and just using the "temporary" rule for them.
This doesn't seem to happen for sites I've added to my "list" of exceptions, though. It only happens when I'm configuring permissions on the fly and just using the "temporary" rule for them.
I've not been doing that that I'm aware, I'll start tryingpjknibbs wrote:The way it currently works in new NoScript is that clicking Trusted only temporarily trusts the site--you'll notice that a large clock icon appears at the end of the button. You have to click on that clock icon to remove it to make the permissions permanent.
If an injury has to be done to a man it should be so severe that his vengeance need not be feared. ... Niccolò Machiavelli
I did that with a few sites, check my list and such to be sure, and then it seemed to get blown out and quirky related to one/two. I just remember it happening and wondering "wtf."pjknibbs wrote:The way it currently works in new NoScript is that clicking Trusted only temporarily trusts the site--you'll notice that a large clock icon appears at the end of the button. You have to click on that clock icon to remove it to make the permissions permanent.
I have noticed that it does seem to handle certain sorts of pages a bit better, but I'm not so confident that it's better than it was in terms of keeping things I don't want happening from happening. Gotta read up on it, I guess.
- red assassin
- Posts: 4613
- Joined: Sun, 15. Feb 04, 15:11
One day you're going to save the world.mrbadger wrote:I just memorised the command line arguments for tar....
No really, and I force my students to use it too
Honestly, since they added the a flag, tar arguments got a lot easier to remember. tar xaf and tar caf are all you need.
A still more glorious dawn awaits, not a sunrise, but a galaxy rise, a morning filled with 400 billion suns - the rising of the Milky Way
Well the problem is now so consistently bad I've just taken to using the temporarily trust all on page button, since it never remembers settings for any site I use, including the one for my own internal NAS....
Advise from the developer involves uninstalling other plugins, but that's a no go, since if I wasn't using them they wouldn't be installed.
It's obviously just a problem with his code-base that needs fixing, not a problem being caused by other plugins. Were this not the case, so many people would not be experiencing identical problems.
Advise from the developer involves uninstalling other plugins, but that's a no go, since if I wasn't using them they wouldn't be installed.
It's obviously just a problem with his code-base that needs fixing, not a problem being caused by other plugins. Were this not the case, so many people would not be experiencing identical problems.
If an injury has to be done to a man it should be so severe that his vengeance need not be feared. ... Niccolò Machiavelli
There's now a proper description to mark the "Temporary" option. And, I didn't know it had updated, either, which pisses me off...pjknibbs wrote:I just noticed that the UI for NoScript has changed again. There are now two buttons for "trust"--one with a clock icon to tempoerarily trust the item, and another one that will permanently trust it.
I got the same notification after the new launch... sort of. IIRC, there were two updates in quick succession and I was notified of the second one...TSM wrote:I got a notification it had updated after the madness of its quantum launch
Does seem to be behaving itself now though.
I did not get notified that it had recently updated in the last few days, though.
You know what I find frustrating? Coders who don't bother with putting "dates" on their changelogs...
"Oh, the app is now in its latest version 1.675308146.92457426.b!"
"But, when did it get updated to that version?"
"I dunno... sometime in 1998."