settings not saved in firefox v57

[glendeni]

I just installed Firefox 57 on Linux (Ubuntu) machine. But I've been having to spend my afternoon trying to deal with NoScript instead of browsing. When an webpage loads I can click to make it "Trusted" and get a green lock icon to appear - but when I restart firefox nothing is remembered and I have to go through the process again. Also tried directly using the "Settings" page - but problems persist.

Some things are so weird that I think that perhaps I don't understand how this is supposed to work. On my own website, after loading a page I click the "S" to get "Trusted", then click the clock (which I _think_ is supposed to make it non-temporary. All seems good, with scripts activated. But then I load the same page in a different tab and find none of the settings I thought I had saved - it says "DEFAULT" and shows the sitename in red.

I had been a user of NoScript with version 56 -and it just worked. But this new version is either buggy or too difficult for me to understand, so I must uninstall NoScript to get any browsing done.

[barbaz]

I click the "S" to get "Trusted", then click the clock (which I _think_ is supposed to make it non-temporary

Bingo.

On my own website, after loading a page I click the "S" to get "Trusted", then click the clock (which I _think_ is supposed to make it non-temporary. All seems good, with scripts activated. But then I load the same page in a different tab and find none of the settings I thought I had saved - it says "DEFAULT" and shows the sitename in red.

Is this website publicly visible?
If so, can you please post the link?

[Pansa]

I just installed Firefox 57 on Linux (Ubuntu) machine. But I've been having to spend my afternoon trying to deal with NoScript instead of browsing. When an webpage loads I can click to make it "Trusted" and get a green lock icon to appear - but when I restart firefox nothing is remembered and I have to go through the process again. Also tried directly using the "Settings" page - but problems persist.

Some things are so weird that I think that perhaps I don't understand how this is supposed to work. On my own website, after loading a page I click the "S" to get "Trusted", then click the clock (which I _think_ is supposed to make it non-temporary. All seems good, with scripts activated. But then I load the same page in a different tab and find none of the settings I thought I had saved - it says "DEFAULT" and shows the sitename in red.

I had been a user of NoScript with version 56 -and it just worked. But this new version is either buggy or too difficult for me to understand, so I must uninstall NoScript to get any browsing done.

Are you serving both HTTPS and HTTP versions on your site?
Are you sure that you link correctly?

A red rule implies that it is connecting to http.
A green rule implies https.

If you make a rule with the green lock and black text, but the site wants to execute via http, it is still blocked.
Hence being red and in default.

If you make a red ...sitename rule, it will permit both http and https. If you want to create path specific rules (the ones starting with http(s)://sitename), you will need both.

[Guest]

I think it's really counter-intuitive to have to click the trusted button once, then click the clock to white list a site permanently. The GUI with its lack of continuity doesn't let the user know that they must make 2 mouse clicks to do the aforementioned. My suggestion is a GUI improvement whereas the user is not forced to make 2 mouse clicks to permanently white list a site. So a greyed out clock means it's permanent, but a not grayed out clock means it's temporary. That just seems really fiddly and finicky, I am sure an improvement can be made over this current GUI which in my opinion really needs work to have the continuity it needs.

[Pansa]

I think it's really counter-intuitive to have to click the trusted button once, then click the clock to white list a site permanently. The GUI with its lack of continuity doesn't let the user know that they must make 2 mouse clicks to do the aforementioned. My suggestion is a GUI improvement whereas the user is not forced to make 2 mouse clicks to permanently white list a site. So a greyed out clock means it's permanent, but a not grayed out clock means it's temporary. That just seems really fiddly and finicky, I am sure an improvement can be made over this current GUI which in my opinion really needs work to have the continuity it needs.

If you see the clock, then it only counts for a time. If you don't see a clock, then time doesn't run out.

As for permanent over temporary as base setting, either way you do it some people are mad.
So the default is the one that gets clicked most often now.
I'd rather have two clicks for permanent than 2 clicks for temporary, seeing as I use the latter way more often.

[nathanpeters]

I think it's really counter-intuitive to have to click the trusted button once, then click the clock to white list a site permanently. The GUI with its lack of continuity doesn't let the user know that they must make 2 mouse clicks to do the aforementioned. My suggestion is a GUI improvement whereas the user is not forced to make 2 mouse clicks to permanently white list a site. So a greyed out clock means it's permanent, but a not grayed out clock means it's temporary. That just seems really fiddly and finicky, I am sure an improvement can be made over this current GUI which in my opinion really needs work to have the continuity it needs.

If you see the clock, then it only counts for a time. If you don't see a clock, then time doesn't run out.

As for permanent over temporary as base setting, either way you do it some people are mad.
So the default is the one that gets clicked most often now.
I'd rather have two clicks for permanent than 2 clicks for temporary, seeing as I use the latter way more often.

+1 for not needing to click twice. I have been using noscript for as long as it has existed, and whenever I chose "allow this page" it remembered the settings. I like the granularity of the new UI, but it needs a little more work.

I actually came here to report this as a bug that it was resetting everything to default every time and then found this post.
Here is the problem with the current GUI: you state that if I don't see a clock, it's permanent. That's not true, I see a small greyed out clock when it's permanent, therefore, there is always some type of clock shown or another.

The other issue with the 2 clocks is that when you mouseover them, they both have the same text. Ie, mouseover the 'temporary' clock brings this tooltip : Temporarily allow (TRUSTED). Mouseover the 'permanent' grey clock also brings up the same tooltip: Temporarily allow (TRUSTED). So the tooltip hint is quite unhelpful. It would be better if at least it showed the current status. Ie, if you are only temporarily allowed the hint should be "This site is temporarily allowed (click to toggle)" and the permanent tooltip should be "This site is permanently allowed (click to toggle)"

[Pansa]

I actually came here to report this as a bug that it was resetting everything to default every time and then found this post.
Here is the problem with the current GUI: you state that if I don't see a clock, it's permanent. That's not true, I see a small greyed out clock when it's permanent, therefore, there is always some type of clock shown or another.

Sure... Be nitpicky about the phrasing.
Obviously it is still there.. Would you rather prefer it being actually gone but still an empty clickable field?
Nonetheless both states are clearly distinguishable as "there" and "away". As in "on" and "off".

The other issue with the 2 clocks is that when you mouseover them, they both have the same text. Ie, mouseover the 'temporary' clock brings this tooltip : Temporarily allow (TRUSTED). Mouseover the 'permanent' grey clock also brings up the same tooltip: Temporarily allow (TRUSTED). So the tooltip hint is quite unhelpful. It would be better if at least it showed the current status. Ie, if you are only temporarily allowed the hint should be "This site is temporarily allowed (click to toggle)" and the permanent tooltip should be "This site is permanently allowed (click to toggle)"

I am unsure whether that is really a thing in HTML.
I agree that the tooltip is not great (although I find the corresponding behaviour for the locks slightly worse).

Nonetheless, the constant complaining about the temp rules with people not even trying to experiment (on a safe site) is a bit grating.
It's a tool that allows you to fudge very specifically with the html you get delivered by website providers, a LITTLE bit of attention is kind of required.

Sure, the tooltip only "hints" at what the clock does. But is "doing it one way, close browser, see result , do it the other way , close browser , see result" for instance on the main google page REALLY too much to ask?
In the context of an addon where you constantly have to decide "is this script an ad, tracking, or the searchbar/video player I wan't to enable or not" maybe a slight bit of trying isn't too much to ask.
It's not like No Script Classic was grandma-safe.

[bo elam]

So the tooltip hint is quite unhelpful. It would be better if at least it showed the current status.

You can tell the current status of a Trusted domain by looking at the size of the clock. Cant miss it. You just have to get used to it.

Bo

[bo elam]

So the tooltip hint is quite unhelpful. It would be better if at least it showed the current status.

Hi nathanpeters, with NoScript version 10.1.5.8rc2, the difference in clock size is even greater now than before. Look at the difference in clock size for Trusted and Temporarily trusted in the picture, easy to tell.



Bo

[nathanpeters]

After getting used to this, I'm actually starting to like the double clock click bit. Maybe old habits just die hard.

The double clock click allows me to click once to see if the page loads and works successfully, then once I confirm that it works, I can 'cement' the settings.

I think it would possibly be more intuitive if you actually did remove the small greyed out clock entirely if the current setting was 'permanent'.