InformAction Forums

Temporary allow and then an afterthought Forbid>>Allow. If there is only one site ,the sticky context becomes invalid as the icon has shifted.In effect an extra page refresh?

nagan wrote:If there is only one site ,the sticky context becomes invalid as the icon has shifted.

Can you explain slowly, for someone whose mother language is not English?

Giorgio Maone wrote: Can you explain slowly, for someone whose mother language is not English?

You have been very modest .The quality of language of yours and other geeks here belies this forum of being purely a technical one and of not an intellectual gathering. Even my mother -tongue is not English.

I have opted for both Status bar label and icon.
Here. I first allow temporarily. Icon shifts to the right as there are no labels now. Then I think of allowing the site permanently. I forbid ,but then the icon immediately shifts to the left. The context becomes invalid now ,as I cannot "ALLOW" the site. Once again I go to the icon click (a page refresh ensues!)and then "Allow". This situation occurs when the icon flip flops because there is only ONE (or the last ONE) site with a scripting nature awaiting permission and given.
I had discussed this in the earlier forum too. Might be the (unnecessary?)rearrangement of icon and labels when the context is ON can be worked out for such situations.

nagan wrote: I have opted for both Status bar label and icon.
Here. I first allow temporarily. Icon shifts to the right as there are no labels now. Then I think of allowing the site permanently. I forbid ,but then the icon immediately shifts to the left. The context becomes invalid now ,as I cannot "ALLOW" the site.

With a clean profile and NS defaults - except that I enabled the same icon/label combo as you describe - I have access to the "ALLOW" context menu item at this step.
I tried it also with the blocked script message bar toggled off. It continued to show the context menu items fine.
Shall go and see if the thing is different in XP 3.5.2
EDIT: No, I can FORBID, then ALLOW in the same sticky context menu with 1.9.8 in XP too.
EXTRA: With Shiretoko in Ubuntu 9.04, the context menu moves back to the left with the icon upon FORBID, and it remains sticky and allows selection of ALLOW without any more refreshes.

I have a different response set.
1.Before allowing anything

2.After temporary allow.

3.Before Forbid.

4.After Forbid.

Hmm, how long has this been going on?
In my tests, the context menu returns to exactly the same position after Forbid as before the original Temporary Allow
Can you reproduce your bug in a clean NS-only profile?

I can't reproduce it in my own custom profile, which has 9 extensions, either.

@GOL
Did you mean that the icon shifted from right to left alongwith the context? There could be a benign page refresh in between? For the cases 3 and 4 of previous post..

nagan wrote:@GOL
Did you mean that the icon shifted from right to left alongwith the context?

Yes. In other words, the context menu is always right above the icon at every point that the icon moves - whereas at your last step - image 4 - the menu is stuck over at the right while the icon has moved back to its original position when the blocked scripts message is shown. It's most certainly stuck all on its own, poor thing. But that wouldn't matter would it? If you could get access to the menu actions?

There could be a benign page refresh in between? For the cases 3 and 4 of previous post..

Whatever refreshes happen, I can always get access to the menu items at any of the steps, but you can't at the last step so...
next test is either with NS on its own, or with a nice shiny clean new profile.
Nobody else has confirmed your bug yet, so would you like to try the usual troubleshooting steps?
Or have I missed something?

Ah, now that GOL has explained it (just whose bug is it anyhow), I can confirm it.

Requires left-click.
Need to change focus to page between Allow/Forbid.

While the "ghost" context menu displays, it will "kind of" work, if you move the mouse over the NoScript icon, at least the fields in the menu will highlight.

There is also a small artifact (that looks to be NoScript too) to the right of the NoScript icon - wait a minute, maybe that is unrelated ...?
Yes it is (related). That is the "empty" Status bar label, i.e., there is nothing for it to show because the site is Allowed, yet there is that artifact.

Quoth therube:

(just whose bug is it anyhow)

Ha! Looks like it's yours now :-)

The status bar "artifact" (Status Bar Label placeholder?) shows here too in the clean profile NS-only test.
The thing "pushes" the icon westwards as it is populated with script messages.
I recall trying to navigate with that combo some time back, and reverting to the separate script message bar because I got annoyed by the jumping icon. It wasn't worth the extra few mm of screen.

therube wrote:Ah, now that GOL has explained it (just whose bug is it anyhow), I can confirm it.

Requires left-click.
Need to change focus to page between Allow/Forbid.

If you click out of the context ,the page will refresh.

therube wrote: While the "ghost" context menu displays, it will "kind of" work, if you move the mouse over the NoScript icon, at least the fields in the menu will highlight.

For me it is dead.

therube wrote: There is also a small artifact (that looks to be NoScript too) to the right of the NoScript icon - wait a minute, maybe that is unrelated ...?
Yes it is (related). That is the "empty" Status bar label, i.e., there is nothing for it to show because the site is Allowed, yet there is that artifact.

Artifact is present by default and empty when all the scripts are allowed.Check out at the bottom right now.

GOL wrote: Whatever refreshes happen, I can always get access to the menu items at any of the steps, but you can't at the last step so...

We are against a page refresh at this point ...Right?

nagan wrote:

GOL wrote: Whatever refreshes happen, I can always get access to the menu items at any of the steps, but you can't at the last step so...

We are against a page refresh at this point ...Right?

Of course the page refreshes at each change of permissions in my setup. That's normal/expected behaviour for NS.
It appears that it will only refresh for therube upon moving the mouse focus outside the stuck sticky menu and back again. And not even that will unfreeze it for you.
So I will back out of the thread now and leave you and therube to isolate the offending underlying cause.
I interpret it as a freeze of the NS context menu when changing from zero active content blocked back to Forbid on a page which has some scripting.

Hmm I wonder what extensions that access layout that both of you have in common and that I don't have?
I still think a clean profile with default NS is a good troubleshoot start because you can establish a baseline to eliminate NS settings first.

Grumpy Old Lady wrote: So I will back out of the thread now and leave you and therube to isolate the offending underlying cause.
I interpret it as a freeze of the NS context menu when changing from zero active content blocked back to Forbid on a page which has some scripting.

Or you can plaintively put it across as "Context refusing to follow the icon when it changes places in a sticky interlude" .

GOL wrote: Hmm I wonder what extensions that access layout that both of you have in common and that I don't have?
I still think a clean profile with default NS is a good troubleshoot start because you can establish a baseline to eliminate NS settings first.

It seems a primitive design bug ,but neverthless would try to do it on a clean NS profile. I do not know what Giorgio has to say ....

Quoth nagan

I do not know what Giorgio has to say ....

Probably busy, as always :-)
Anyway, why not help him when he gets to the thread, by doing the elimination of settings and/or other addons?
You're in the driver's seat here. And therube if you can persuade him :-)

It's nothing really to deal with, simply a bug.

(I'm not sure my "focus" comment was particularly accurate?)

URL: http://www.nitdgp.ac.in/

First you Allow.
Then after the Forbid, the Context Menu (ghost) is incorrectly positioned & so does not react to input.

This only happens if you have the Notification Bar (is that what it is called), Show message about blocked scripts -> at the bottom enabled. Disable that, & it works as expected.

Context Menu incorrectly positioned, it is a "ghost", & is ineffectual:



When mouse is at the same vertical position as the NoScript icon, you see the Context Menu ghost does highlight & is at least partially effective.



And actually you can position the mouse to the left of the NoScript icon, up to the width of the context menu & even out there it is still partially effective. (Most actions may not work, but you can expand the Untrusted menu & you can actually mark nitdgp as Untrusted.)