NoScript v10: customizability of the popup window - ideas

Post a reply

Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: NoScript v10: customizability of the popup window - ideas

Re: NoScript v10: customizability of the popup window - idea

by aleister » Sun Jan 28, 2018 12:26 pm

Hello. Quest You have written, that: "I don’t want any customizability there". OK, but don't You think, that writing about something in such a way - without using, trying or even saw this - is pretty... strange? I do understand your point of view, but I think, that we should check something before making an opinions etc.

Generally, an idea is about listing allowed capabilities on a specific preset/option and so on. (See my first post, for example, and: Allowed caps.: fetch, other, media, font. That's a "menu" or caps informations after clicking on NoScript icon, next DEFAULT preset etc.) Of course, there can not be made any changes. Just as it's now. And if there no capabilities are allowed, there can be something like: Allowed caps.: none and so on.

I think, that it can be very helpful to easy check what caps are allowed etc. Now, after clicking on NoScript icon, next - for example - DEFAULT, nothing happens.

Thanks, regards.

Re: NoScript v10: customizability of the popup window - idea

by Tomatix » Mon Jan 15, 2018 11:39 pm

Quest wrote:I don’t want any customizability there, but may I suggest a tiny rearrangement:

Left to right: Default Untrusted Trusted TempTrusted Custom

At least two advantages:

1. Aesthetics : Reds and blues not mixed
2. Logics: Global “fixed” settings and the others not mixed
3. Usability: When you open the menu you probably click (if at all) only Custom or TempTrust and then maybe Trusted so it’s better that they are nearest (from the point where “you are" after opening the menu.)
My opinion on this:
1. I don't think that's really beneficial. ;)
2. I think its best to use freq. of use order logic from left to right here (as it is).
3. With the current layout: You need to put the NS icon on the left side, then you truly have minimal mouse movement.

Re: NoScript v10: customizability of the popup window - idea

by Quest » Sat Jan 13, 2018 12:07 pm

I don’t want any customizability there, but may I suggest a tiny rearrangement:

Left to right: Default Untrusted Trusted TempTrusted Custom

At least two advantages:

1. Aesthetics : Reds and blues not mixed
2. Logics: Global “fixed” settings and the others not mixed
3. Usability: When you open the menu you probably click (if at all) only Custom or TempTrust and then maybe Trusted so it’s better that they are nearest (from the point where “you are" after opening the menu.)

NoScript v10: customizability of the popup window - ideas

by aleister » Fri Jan 12, 2018 6:05 pm

Hello. First of all: I don't know if it's a good idea to create a new thread, because there was an update to the v10.1.6.3 version with some improvements related to capabilities highlighted, customization etc. (please see: NoScript v10: revert back the customizability popup?) (However, if Barbaz will decide to merge this post with my earlier thread, OK.)

I want to show, propose something new to the NoScript main popup window - it's related to an idea mentioned in above thread (see: "NoScript v10: revert back the customizability popup?" thread): show/list allowed capabilities. (I can not make a screenshot, sorry). So, here is a popup window (I've choosen "DEFAULT" as an example), that's showing capabilities set by the user (NOTE: it shows the moment when an user clicks on the NoScript main icon, next "DEFAULT" preset/option):

Code: Select all

,-------------
|(S) Default  ) (S)Temp. TRUSTED  (S)TRUSTED  (S)Untrusted  (S)Custom
|              -------------------------------------------------------------.
| Allowed: fetch, other                                      (Configure...) |
'---------------------------------------------------------------------------'
There can be also a "Configure..." button, next to the caps list, to easily access NoScript "Options..." window to make necessary changes etc. NOTE: Allowed: can be changed to/with: Allowed caps.: ('caps.' stands for 'capabilities') As we can see, there are capabilities list when user click e.g. on a "DEFAULT" preset button. Of course, nothing can be changed here - it's just a main NoScript popup window and list of the capabilities allowed by the user etc. Nothing more, nothing less.

Now, if user will made some changes in NoScript "Options..." windows; for example he will add "media" and "font" options to the "DEFAULT", then main popup window will be changed/updated, of course:

Code: Select all

,-------------
|(S) Default  ) (S)Temp. TRUSTED  (S)TRUSTED  (S)Untrusted  (S)Custom
|              -----------------------------------------------------------------------.
| Allowed caps.: fetch, other, media, font                             (Configure...) |
'-------------------------------------------------------------------------------------'
As we can, Allowed: was changed to Allowed caps.: - just for an example. A list of capabilities can be grayed out, or something. NOTE: It seems, that these popup windows examples looks better with a <code></code> tags. However, I can not use colors, bolding etc., to make it looks even clearly.

By the way: because "UNTRUSTED" option (which is often considered with the lack of any capabilities changes), allows to set three values only, such as: "media", "frame", "font" I think it also should be treated as a "DEFAULT" option etc. I mean showing capabilities and so on.

One more thing: clicking on a "Configure..." button will open NoScript "Options..." window allowing user to make an additional changes, to check or un-check another capability and so on. Just as it is now. It seems to be pretty simple. Here are some more ideas:

✗ change "Allowed:" to "Allowed caps."
✗ change "Configure..." button with "Configure caps." (if, for example, Allowed: is in use etc.)
✗ capabilities list can be grayed out

So, what do you think? I'm sorry if all of this is pointless and have no sense, but I hope that I managed to present this idea clearly.

Mr Maone, thank You very much for all your work on the NoScript etc.

Top