NoScript Options Fails To Open, Sometimes

[therube]

NoScript Options Fails To Open, Sometimes

Perhaps this?

Code: Select all

Error: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [xpcIJSWeakReference.get]
Source File: chrome://noscript/content/noscript.js
Line: 49

49:

Code: Select all

    let od = odRef && odRef.get();

In case it has any bearing, when I've seen this, I've had two separate instances of SeaMonkey open.

One fullscreen (maximized that is, rather then F11 "full").
The second, half screen, overlaying the left half of screen one.
And I'll attempt to open Options from the NoScript icon on screen one.

And sometimes, it does not open.

[Hecuba's daughter]

Confirmed as an itermittent bug. I hadn't noticed the connection between the changed state of the window, but that is definitely what seems to be connected.
Latest dev NS
ESR latest in Win 7
New clean NS-only profile
Open new instance - all FX/NS defaults
This brings up what Fx decides is the best size for the display (i've given up arguing with all those settings ha!) about 2/3 of the screen.


Open a maximised window (not F11)
Invoke NS Options. Options window opens.
Return to 2/3 screen size window, invoke NS Options. Sometimes Options window fails to open.

Mostly the Options window doesn't open at first invocation, but then opens at second and following invocations.
Sometimes it will open first, but if I change to a different invocation - eg, use context menu instead of toolbar button - then it sometimes won't open again that first time, followed by working ok again.
Minimize to Win notification bar, maximize from there, invoke Options - first try usually won't work.

The line 49 error only shows when the bug does.

[therube]

I've had two separate instances of SeaMonkey open.

MIght it be this rather then overlapping windows?
Saw it again & this time the window was maximized, no overlap.

[barbaz]

Are you still seeing this? Because I had this problem also, on Linux, but seems it's been gone here for a while.

It's nothing to do with window maximized or multiple windows or multiple browser instances, because I saw this with only a single, non-maximized browser window open. Didn't think to check the Error Console though, because at the time I thought it was user error, but then I saw this thread - and couldn't reproduce the issue since.

[therube]

> Are you still seeing this?

Can't say I've noticed it of late.
Though that doesn't mean it isn't still an issue, I may just not have run into it again?