minor scroll issue

[JGns]

Hi I would like to report a minor UI issue I noticed in NS 2.2(stable and rc3) context menu. I'm using Fx 8.0.

When a site has enough scripts listed to enable the scroll buttons on the NS context menu I noticed that in addition to the small scroll buttons at the very top and bottom of the menu the mouse wheel can be used to scroll down. However scrolling up doesn't work at all. I know this is a very minor issue, just though it should be mentioned.

I'm reluctant to post a link to any site because it will probably vary depending on screen resolution and dpi, it just has to "overflow" the context menu so that scrolling is enabled.

Once you have enough listed in the menu try to scroll up with the mouse wheel(doesn't work for me) then hover over the little scroll button at the top of the menu until it hit the top and then try to scroll down with the mouse wheel(does work for me).

... Just in case anyone ask my mouse wheel works fine in both direction in Fx and every other application I tried.

[Tom T.]

Hmm... I use only laptops with no scroll wheel, so can't comment on your issue, but the post brought to mind another idea for a modest RFE.

It really is quite annoying when the script list runs off the screen. Perhaps there could be a "MORE" after some number of listings. Either by reading screen resolution and size, if that's available without active sniffing; else, just some arbitrary number. Ten? Twelve? ... You would point to MORE to see a side-by-side menu open up, somewhat comparable to "Start" in Windows, except that there, you're pointing to a sub-menu group, such as "Programs". Here, you're just getting all of the listed scripts and objects (plus Recently Blocked pointer, Blocked Objects pointer, Temp-Allow All/Revoke Temp, Untrusted pointer, etc.) on the screen at the same time. Which would be a major improvement, IMHO.

It could go to three rows if necessary -- yuk, but it happens.

And would still open another row to the left of these when you point at, say, "Blocked Objects".

I'd like to see "Options" be the first entry instead of the penultimate one, so that it's always visible without scrolling or additional menus per this RFE.

"About NS X.x.x.x" can remain the last one. The functionality of Options, blocked scripts and objects that might need to be allowed, etc. should take priority over the "About NS" entry, IMHO.

Thanks for bringing this up.

ETA: Rather than bothering with varying screen sizes, etc., be user-configurable. Something like:

Code: Select all

noscript.menu.max.items (Integer)  (default #)

And if not too much more trouble, GUI on Appearance tab (upper right still has room):

Code: Select all

Open second menu when first menu reaches (default #) items

... with increase/decrease arrows if not too much trouble; else, user just pastes desired value over the default.

Default at about 10-12 or so? .. And blocked scripts count as two entries, since they have both "Allow" and "Temp-Allow"? -- whereas items like Untrusted, Recently Blocked, Options, etc. are counted as one item.

[JGns]

Yeah it can be quite annoying at times . I can see pros and cons to your idea.

pros
Less options hidden
Reduces the need for scrolling

cons
It might take a little time getting used to reading independent columns; it could have a "wall-of-text" effect.


In any case those are just my opinions, the opinions that matter are those of the coders and a majority of users.

[Tom T.]

In any case those are just my opinions, the opinions that matter are those of the coders and a majority of users.

Exactly. And since no users have expressed any input in the couple of days that this has been up (still welcome, of course), I've already asked the coder (singular -- NoScript is Giorgio Maone's baby; it's all his) to take a look at both of our posts.

I'm sure you understand that his higher priorities are security fixes and enhancements, major bug fixes, bringing NS 3.x to the desktop, etc.
But if he hasn't replied in, say, a week or so, I'll send him another gentle reminder.

If I forget, you can send me one. Just post, "Any response yet?", or something like that, and I'll get an auto-notification by e-mail that serves as a good reminder among all the threads tracked.

Thank you for your patience.

[JGns]

Ok, thanks for letting me know.

It was really just something I noticed and thought was strange. I do understand that it is a very minor and innocuous issue, but just wanted to put it out there.

I'm a happy NS user even if it stays as is .

Thanks for all of your help!

[Tom T.]

Agree with your assessment of my suggestion, with a couple of minor exceptions:

pros
Less options hidden
Reduces the need for scrolling

Ideally, *eliminate* the need for scrolling altogether. ... unless you mean that you use the scroll wheel to move the mouse pointer, although IIUC, that's not what was meant.

cons
It might take a little time getting used to reading independent columns; it could have a "wall-of-text" effect.

It's definitely a change in NS behavior, but Windows users are already well-acclimated to multi-generational menus and the amount of screen covered by them.
Mine came OOB with *four* generations of menus (from "Start") which I've pared down to two.

Tip: Find as many scripts as you can that can be marked "Untrusted"; then, they won't show up in the main menu ever again. (If you need to re-enable, temp or otherwise, point to Untrusted, then to the desired source.) This shortens menus greatly, as most of the long menu lists include pretty much the same lists of advertisers, trackers, etc.

O/T Hot tip: Anyone want to know how how to reduce or eliminate the 0.4 sec default delay in opening the next generation of Windows menus? Some users are a little freaked out with less than 0.1 - 0.2, but setting it to *zero* is highly entertaining, running the pointer up and down and watching the second menus zip by. (Little things amuse little minds. ) .. and seriously, it's faster navigation to the target.