[RESOLVED] Changed mouse focus?

[barbaz]

Yes

[barbaz]

This is reproducible in Firefox 36 release in Linux.

[barbaz]

Oh, and NoScript 2.6.8.14 works as expected.
(not necessarily an exact regression range)

EDIT The earliest NoScript version with this issue is 2.6.8.21rc1. Looks like this issue was supposed to have been fixed in 2.6.8.23 but that fix got broken by Firefox 36.

[cumdacon]

what to do?
viewtopic.php?f=10&t=20581

[barbaz]

All there is to do is wait for Giorgio to fix it.

[cumdacon]

I agree with you.
Thanks.

[cumdacon]

Bad news.
2.6.9.16, just released,
does NOT resolve the defocus issue
(Now I am worried).

[barbaz]

Why are you worried at this point?

v 2.6.9.16
=============================================================
+ [Surrogate] Updated Gravatar surrogate (thanks barbaz)
+ Additional HTML sanitization when pasting rich text into
content-editable elements (thanks .mario for RFE)
+ Introduced framework for E10s migration, starting with new
features and fixes
x Removed deprecated let () expressions from the code base

Giorgio just hasn't gotten to this bug yet and those fixes were deemed important enough to make another release.

[cumdacon]

I am worriend because Giorgio was use to resolve in few minutes.

[Thrawn]

I am worriend because Giorgio was use to resolve in few minutes.

For important security fixes (like bypassing the XSS filter) he does.

[cumdacon]

this defocus is annoying.
we wait and we hope

[cumdacon]

2.6.9.17.

[Giorgio Maone]

I'm having a hard time at reproducing this issue, but it's just probably that I couldn't understand it correctly.

What I'm doing:

1. On a clean Fx 36.0.1 profile, installed NoScript 2.6.9.17rc2
2. Open https://noscript.net/
3. Hover the NoScript icon (its menu opens), select "Forbid noscript.net" - the menu stays on the screen, no reload happens until I the menu loses focus.
4. Select "Allow noscript.net" - since this is the only script origin in the menu, it closes immediately and the page gets reloaded

The menu can be dismissed by clicking on any content or chrome area outside, in order to defocus it.
This is the only difference which I can observe if comparing with past behavior, when the popup menu got defocused and closed automatically when the muse pointer exited its area. This is due to changes in Firefox 36, rather than in NoScript, but I tend to consider it a progress, albeit accidental, rather than a bug: I actually used to hate the menu disappearing in the middle of a complex permission setting operation because the cursor was went in the wrong position. Explicit clicking to dismiss seems reasonable in most circumstances and really helpful in some, and it's how most toolbar menu seem to work now anyway.

[cumdacon]

The menu can be dismissed by clicking on any content or chrome area outside, in order to defocus it.

a new (very bad) feature of noscript?
progress? oh no, I dont want to use this "ameliorament".
when you do tasks in noscript menu you should be aware with the mouse. I dont agree with this behaviour.
mouse on the tooltip = perform tasks in noscript, otherwise the menu should disappear instantaneous to allow the page to be reloaded. An additional click (or double click: the one for re-obtain the focus + another for "real" click on a link) is unacceptable.
the more clicks = the more modern interface = more convenient ? for me it isnt.

[barbaz]

The menu can be dismissed by clicking on any content or chrome area outside, in order to defocus it.
This is the only difference which I can observe if comparing with past behavior, when the popup menu got defocused and closed automatically when the muse pointer exited its area. This is due to changes in Firefox 36, rather than in NoScript, but I tend to consider it a progress, albeit accidental, rather than a bug: I actually used to hate the menu disappearing in the middle of a complex permission setting operation because the cursor was went in the wrong position. Explicit clicking to dismiss seems reasonable in most circumstances and really helpful in some, and it's how most toolbar menu seem to work now anyway.

Just to clarify, that is exactly the bug in this thread.
Please don't consider this bug a feature. Personally I find the new behavior *very* annoying (luckily for me, my everyday browser is SeaMonkey 2.32.1 so I don't have to deal with this yet).
Until now, it has *always* been that you had a choice whether you wanted the menu to close on click or on mouseout - for the former you click the icon; for the latter, you just hover over the icon. I liked that, and there is no reason to take that choice away from users if that choice can be given under Firefox 36's limitations.

Please, bring back that old behavior if possible so that all can once again have their NoScript menu the way they like. Thanks!