InformAction Forums

V 2.6.9.39
Some websites like e.g. those of newspapers have a huge amount of scripts.
The usual thing I do is to iterate

(temporarily) allow all this page

as described in the NoScript FAQs.
I always want to keep track of what I have allowed, so I have most of the Options | Appearance items active.
Therefore the menu becomes crammed with "Forbid <allowed thing>"
This makes the option "(Temporarily) allow all this page" (among others) hard to reach, as it disappears from the screen, being it placed *after* all the "Forbid" items.

My question: is it possible to have the items "(temporarily) allow all this page" closer to the beginning of the contextual menu, hence to the mouse pointer?
One step further: could one decide in which order the items Options | Appearance should appear?

Thank you very much for your time.

(If that's what you're doing, TAA, repeatedly, then you could use the shortcut key, Ctrl+Shift+\, instead of using the menu.)

Thank you all.

It is true that when TAA is involved, I practically don't mind looking in the blocked script list. Therefore the keyboard shortcut is definitely OK.

I understand there is no support for this customization yet (I could not find the menuOrder property, and setting it as explained does not change the order), but someone has already started the discussion.
I looked thoroughly the FAQ but not so thoroughly the other forum topics. I beg your pardon.

gapag wrote:I understand there is no support for this customization yet (I could not find the menuOrder property, and setting it as explained does not change the order)

Because as you found out it's not implemented yet, that's just a detailed RFE at this point.

gapag wrote:I looked thoroughly the FAQ but not so thoroughly the other forum topics. I beg your pardon.

np

Greetings all! Great and noble work. I just registered to pose this feature request but I see it's already here.

It would be nice if there was an about:config option to place the static section items (eg, Temporarily allow) on the INSIDE of the menu rather than the OUTSIDE. The INSIDE being the part that is closest to the menu click point. I use inside/outside instead of top and bottom to clarify because if the NoScript icon appears at window bottom the menu is mirrored vertically.

Thanks to TheRube for pointing out the shortcut key, and like gapag I too like to glance at the the blocked list with a hacker's interest, and will probably be doing so even as I prepare to use the shortcut key.

But I'm making this plea for my Dad. NoScript has been a hard sell for him. He lives in an RV and has a floating screen, places the mouse on his knee or the couch and surfs from bookmarks and links, most often has the keyboard tucked aside. These days when you land on a blank js page you are most often one TempAllow away from seeing text content, but several TempAllows away from getting a media clip to play. I was able to sell him on NoScript more on the idea of improved performance than security, he's a lamb in the woods... but frankly scrolling menus with the tiny scroll region on the bottom is a pain, but for him it's almost impossible with his level of mouse control.

"Temporarily allow? It's not here."
"You may have to scroll the menu to see it."
"How do I do that?" (for the third time)
(Then later, because we will have to go three TempAllows deep)
"You mean I have to do that again??"
(Then later, when I explain the shortcut key)
"I don't keep the keyboard on my lap. Maybe we should turn this thing off."

Please... in a way this is an accessibility issue. When you click on a menu 'static/global' options should always be visible immediately and easily accessible. NoScript through no fault of its own has allowed its menu to become a dynamic document that has predictably become spam'd by the content providers. These block lists often exceed the vertical height of the window and require scrolling.

My Dad will never reach the level where he's evaluating individual allow/deny items, but with a mouse-accessible TempAllow I can manage to convince him not to AllowGlobal.

@PartyHeartyHarry: You really should give your dad Cascading Permissions mode, where all he does is Temp-Allow the top-level site and all scripts on that site are Temp-Allowed. Much fewer clicks for the same result.