NoScript v10: revert back the customizability popup?

Ask for help about NoScript, no registration needed to post
aleister

NoScript v10: revert back the customizability popup?

Post by aleister » Wed Jan 03, 2018 4:52 pm

Hi. It could be a Request, but... I would like to know your opinions etc.

I would like to ask about a new feature in v10.1.6.2rc1; I mean "removed customizability of DEFAULT, TRUSTED and UNTRUSTED preset from the popup" etc. Earlier, it was possible to check/uncheck - for example - DEFAULT options, right? Now, it's impossible. Good, I understand the reason behind such decision.

Now, if user wants to check what is allowed or denied, he have to - for example - click on the NoScript icon, next click "Options...", and next check "Debug" option. It seems to be a little difficult for beginners. Don't you think? Maybe, it would be better if "customizability" of the above preset can be reverted back? Of course, I mean without possibilities to check and uncheck all options - I mean without changing this feature found in v10.1.6.2rc1 release.

Just to make it easier to check or see what's allowed and denied etc. (Just like it looks, for example, here: screen -- It is an old screen, when options modifying were still allowed.) It can be, for example, grayed out or something? I mean an options on a popup window (please, see an above screen). Just to make it a little bit easier...

And probably most important thing: with this new feature from v10.1.6.2rc1, users can not see the red highlighting (which are showing the capability, that have been detected in the page etc.) Such a possibility was available before.

By the way; it seems, that there is a similar thread (see: No more preset checkboxes for global scopes?) but in my case it's rather a small REQUEST (for opinions etc.), not question. So, I don't know if these thread should be merged. But decision is up to You, Barbaz.

Thanks.
Last edited by barbaz on Wed Jan 03, 2018 5:14 pm, edited 2 times in total.
Reason: By request
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0

barbaz
Senior Member
Posts: 9262
Joined: Sat Aug 03, 2013 5:45 pm

Re: NoScript v10: revert back the customizability popup?

Post by barbaz » Wed Jan 03, 2018 5:11 pm

aleister wrote:Maybe, it would be better if "customizability" of the above preset can be reverted back? Of course, I mean without possibilities to check and uncheck all options - I mean without changing this feature found in v10.1.6.2rc1 release.

Just to make it easier to check or see what's allowed and denied etc. [...] It can be, for example, grayed out or something? [...]

And probably most important thing: with this new feature from v10.1.6.2rc1, users can not see the red highlighting (which are showing the capability, that have been detected in the page etc.) Such a possibility was available before.
Interesting request.

Related: https://forums.informaction.com/viewtop ... =7&t=24340
aleister wrote:decision is up to You, Barbaz.

Thanks.
I haven't seen anyone else make this specific request, so starting a new thread was the right thing to do.
*Always* check the changelogs BEFORE updating that important software!
-

aleister

Re: NoScript v10: revert back the customizability popup?

Post by aleister » Wed Jan 03, 2018 5:12 pm

Sorry, I've made a fatal mistake. In a place where "Now, if user wants to check what is allowed or denied, he have to... (...)" sentence is, it should read: "Now, if user wants to check what is allowed or denied, he have to - for example - click on the NoScript icon, next click "Options...", and next check "Debug" option. It seems to be a little difficult for beginners". This is obvious, because there is another, simpler way to check these options: NoScript Options... window! There is no need to use a Debug option/window.

I apologize for that mistake and one more thing: at the very end of my post, there is a double sentence: "So, I don't know if these thread should be merged". Of course, one of these sentences should be removed.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0

barbaz
Senior Member
Posts: 9262
Joined: Sat Aug 03, 2013 5:45 pm

Re: NoScript v10: revert back the customizability popup?

Post by barbaz » Wed Jan 03, 2018 5:14 pm

^ Should be fixed now :)
*Always* check the changelogs BEFORE updating that important software!
-

Guest

Re: NoScript v10: revert back the customizability popup?

Post by Guest » Wed Jan 03, 2018 5:26 pm

Sure, it is fixed now! Barbaz, thank You very, very much for making all these specific changes in my first post (duplicate sentences, link repair etc.) Many, many thanks! :- )

Cheers. (aleister aka daniel4859)
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0

Pansa
Senior Member
Posts: 318
Joined: Fri Nov 24, 2017 10:30 pm

Re: NoScript v10: revert back the customizability popup?

Post by Pansa » Wed Jan 03, 2018 7:02 pm

It's not just in the debug output:

https://forums.informaction.com/viewtop ... 10&t=24336

It was changed because people complained that it was confusing and a security risk, because it was too easy to access.
Now it's more hidden, so people who didn't think it was confusing or a security risk remark that it is counter-intuitive to find (which it is).

Personally, either has a point, but the earlier version was visually and logically consistent, and the new one is less so.
And that's how I personally understand "intuitive". Others define it as "I personally don't have to think about it", but that overlaps too heavy with "I learned it one way and everything else is bad" for my taste.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

aleister

Re: NoScript v10: revert back the customizability popup?

Post by aleister » Thu Jan 04, 2018 11:09 am

Hi Pansa; "It's not just in the debug output" - yes, we know that. And that's is the reason why Barbaz added "for example" in this sentence: "Now, if user wants to check what is allowed or denied, he have to - for example - click on the NoScript icon, next click "Options...", and next check "Debug" option" (see my first post). Also, I wrote later, that "There is no need to use a Debug option/window".

But thanks for your opinion on this :- )
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0

Quest

Re: NoScript v10: revert back the customizability popup?

Post by Quest » Thu Jan 04, 2018 12:03 pm

I really can't see why settings which you never have to change should be easily accessibe.
And I'd really don't care if I'll never found them once I've set them.

But of course there should be some logical way to access them. This new one is not.
There still is no need to chance those options on every item on the white list. One place would be enough and besides easy way to check what those settings are. (Although I don't get why you should check or set them on daily basis. Are those who insist this really understood what they are doing?)

Does Webextensions prevent from doing any kind of "classic" menu, for example where these options (the yellow bar thing or something similar) appears after you press the Global Settings button?
Mozilla/5.0 (Windows NT 6.1; rv:57.0) Gecko/20100101 Firefox/57.0

aleister

Re: NoScript v10: revert back the customizability popup?

Post by aleister » Thu Jan 04, 2018 2:51 pm

Hi Quest. Honestly, I'm changing options pretty often to find the best settings etc. (An example: youtube.com needs googlevide.com to work, right? But it needs only fetch option, not all.) I think less working options, is a better solution than allowing all of them. Once again: I'm thinking about NoScript settings/options, that allow website to work correctly. It's only my personal opinion! And I think, that many - more advanced - Users do the same thing etc. But maybe I'm wrong...

"And I'd really don't care if I'll never found them once I've set them." - that's OK, your choice :- ) As I already wrote: just make things a little bit easier, e.g. for beginners users and so on.

Thanks for your opinion, Quest.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0

jawz101
Senior Member
Posts: 68
Joined: Sun Jul 10, 2011 11:13 pm

change in 10.1.6.2rc1 lost ability to see what's blocked

Post by jawz101 » Thu Jan 04, 2018 3:52 pm

Sorry for the crappy title. I couldn't write it out. Anyways. This change:
- Removed customizability of DEFAULT, TRUSTED and UNTRUSTED
preset from the popup (reported as a major source of
confusion) while keeping it in the Options tab
... I understand but I just realized it has crippled my ability to troubleshoot how those presets' blocks. I keep Default and Trusted pretty minimal (Default gets fetch. Trusted just gets fetch and script. I use custom for anything more.)

Whenever the Default group isn't enough I can't tell what it might be blocking as I cannot see what items are being blocked by its policy. The workaround so far that I have is to move the site to custom, I can then see what turns red on a refresh, and then adjust the permissions accordingly.

I can keep doing that but it doesn't feel like it's giving me the ability to troubleshoot domain policies too well.

Instead of suppressing the preset customization options can you make them read-only on the popup? That way you can still see what was blocked by them. That, or any other way to troubleshoot blocked.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0

barbaz
Senior Member
Posts: 9262
Joined: Sat Aug 03, 2013 5:45 pm

Re: NoScript v10: revert back the customizability popup?

Post by barbaz » Thu Jan 04, 2018 4:48 pm

Threads merged.
*Always* check the changelogs BEFORE updating that important software!
-

aleister

Re: NoScript v10: revert back the customizability popup?

Post by aleister » Thu Jan 04, 2018 6:09 pm

Hi jawz101. You wrote, that "The workaround so far that I have is to move the site to custom, I can then see what turns red on a refresh, and then adjust the permissions accordingly". That's true, but i think there is one more method to see what is blocked etc/to see what is being blocked.. (I hope, that I understand this NoScript mechanism well.) Anyway, here is an example:

There is an example.com website, which is not working correctly, properly. My NoScript's DEFAULT preset policy is like this: [other], [fetch]. (Everything else is un-checked.) When I move mouse cursor on NoScript icon (but not clicking!), there is a small popup window, menu:

NoScript (19/19)
<script>: (19/19)

As we can see there is a [script] option, right? So, after change NoScript policy for this website to e.g. Temp. TRUSTED or after adding [script] to the DEFAULT preset (which I'm trying to avoid), after website reload everything start to work properly! The same thing with other showed options - for example [object] etc. If there will be [object] on the above small popup window, then I should also allow [object] option and so on.

By the way: in my opinion, it's better to use Temp. TRUSTED option instead of adding [script] to the DEFAULT.

jawz101, I hope, that it will help you somehow.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0

User avatar
Giorgio Maone
Site Admin
Posts: 8732
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: NoScript v10: revert back the customizability popup?

Post by Giorgio Maone » Fri Jan 05, 2018 12:20 am

Please check latest development build:
v 10.1.6.3rc2
=============================================================
x Moved preset customization into its own (more discoverable)
global Options section, rather than embedded in assignment

x Domain matching now threats unknown no-dot domains (not in
the public suffixes list) as TLDs everywhere
x Improved validation of manual entries
x Needed capabilities highlighted also on short-hand domain
matched entries inside the CUSTOM preset
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Tomatix
Senior Member
Posts: 60
Joined: Tue Dec 05, 2017 3:05 pm

Re: NoScript v10: revert back the customizability popup?

Post by Tomatix » Fri Jan 05, 2018 1:44 am

Giorgio Maone wrote:Please check latest development build:
v 10.1.6.3rc2
=============================================================
x Moved preset customization into its own (more discoverable)
global Options section, rather than embedded in assignment

x Domain matching now threats unknown no-dot domains (not in
the public suffixes list) as TLDs everywhere
x Improved validation of manual entries
x Needed capabilities highlighted also on short-hand domain
matched entries inside the CUSTOM preset
Nicely done IMO.
Dedicated section signalizes the importance of these checkboxes. Avoidable confusion eliminated. :D
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0

Post Reply