1.9.5 kills Snap Links Plus

[Wilson]

Not suspecting Noscript would have anything to do with opening links, this was the last of my dozen addons I disabled, and the ultimate culprit. Snap Links is kind of in limbo, and underused, but hopefully this is causing other problems (like the person trying to "open all in tabs"?), and can be fixed.

[therube]

Link: Snap Links Plus 1.0.2
The older variety: Snap Links 0.0.4
And another: Snap Links [FF3] 1

I don't look to have any problem here:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090206 Minefield/3.2a1pr
Nor here:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090617 SeaMonkey/2.0b1pre

NoScript 1.9.5.1 SLP 1.0.2

[Wilson]

Thanks for your reply. With more testing it seems that Noscript 1.9.5-1.9.5.2 really slows things down when you try to open multiple links. Selecting just a few links works OK if you go slow; selecting 10 might only open a few unless you pause several seconds and keep the mouse steady; selecting 100 is almost impossible, with the tabs opening in batches--3 open, a pause, 3 more, etc. This is probably the same problem as "anonymous noob" who can't open a lot of bookmarks at once.

[therube]

I do not see a slowdown issue per say.
URL for your 100 links?

At times, what I have found with longer selected lists, is that only so many will open, others will be left unloaded.
(I noticed this well before the advent of ABE.)

Now I wonder if that is a browser limitation, a limitation of Snap Links ... or ...

Hmm. I never even considered NoScript even after reading this thread a number of times - until now.

URL: http://www.pcqanda.com/dc/dcboard.php?a ... how_topics

(Too make the listing more concise, select, 'Choose classic view' & 'Collapse topics'.)

30 threads should be displayed.

Leave NoScript enabled.
Snap all 30 links.
Only 9 or so open for me.

Disable NoScript & repeat.
All 30 links open.

Interesting.

[LinkSnapper]

I also have disabled one extention after the other until I found out that noscript is causing the problem with snaplinks. I also can confirm that opening many links at once has become very slow (regardless whether those are opened with snaplinks or by single middle-clicks). To me it appears as if this immense slowdown is what causes the trouble with snaplinks -- because it's selection rectangle also needs much time to disappear now while snaplink is opening links several times until I move the mouse outside of the firefox window. So probably this is somehow related. I hope this can be fixed soon, as both are very important extentions to me and I don't want to stop using any of them.

[therube]

Well color me baffled

My SnapLinks observations above were in FF35 with SnapLinks 1.0.2.

At times, what I have found with longer selected lists, is that only so many will open, others will be left unloaded.
(I noticed this well before the advent of ABE.)

Now that deals with SeaMonkey 1.1.17, in one particular Profile.
(I'll have to check that one a bit later.)


So now I take a different SeaMonkey 1.1.17 Profile.
I put in NoScript & a modded version of Snap Links 0.0.4. (Has to be modded, or else it wouldn't run in SeaMonkey 1.1.17.)

And I run the same tests in that Profile:

Leave NoScript enabled.
Snap all 30 links.
Only 9 or so open for me.

Disable NoScript & repeat.
All 30 links open.

Only problem is, I get different results.
Regardless of NoScript, all 30 links open as expected.
And to top it off, they appeared to load a bit better when NoScript was installed.

[therube]

To me it appears as if this immense slowdown is what causes the trouble with snaplinks -- because it's selection rectangle also needs much time to disappear now while snaplink is opening links several times until I move the mouse outside of the firefox window. So probably this is somehow related.

I think you're on to something here. But don't know that it's NoScript? And maybe it is not at all?

I believe it is differences in Gecko 1.8 vs 1.9.

In Gecko 1.8 it looks as if ALL the links are fired at once, the green selection rectangle disappears almost immediately.

In Gecko 1.9 it looks more systematic. A tab fires, the next fires, the next fires ... Now once it starts opening tabs, so long as you do not move the mouse, the selection rectangle remains until all the tabs have fired, & all (30) will open. BUT, if you do move the mouse ahead of time, at that point the selection rectangle disappears & only those that happened to get fired while the rectangle existed are opened. The rest fail to load.

So if you were to try in FF2, I would expect similar results as to SeaMonkey 1.1.17.

So if you were to try in FF2, I would expect similar results as to SeaMonkey 1.1.17.

True.
So to me, it looks to be a Gecko issue rather then NoScript related. (See how observations can at times skew the truth.)

Perhaps Gecko 1.8 is firing asynchronously, & Gecko 1.9 is firing synchronously?

(al_9x, you listening. Maybe a bug should be filed on this?)

Now, in the same manner, that also does not mean that NoScript is not affecting things in Gecko 1.9 ... (I ain't done yet ...) ...



So ... yes it does look like NoScript is affecting things in Gecko 1.9.
Once I uninstall NoScript, in SeaMonkey 2 (Gecko 1.9.1), SnapLinks 0.0.4 (has to be the modded version in SeaMonkey), then at that point the links open as they do in Gecko 1.8.


So NoScript does not affect SnapLinks in Gecko 1.8, but it does affect SnapLinks in Gecko 1.9.

That's the way I see it at this point. And I'm sticking to it!

(al_9x, you listening. Maybe a bug should be filed on this?)

Or may it in fact does belong here (NoScript).

[Giorgio Maone]

Can you check latest development build 1.9.5.4?

[therube]

Batting 30 for 30 .


Works now like it does in Gecko 1.8.
The selection rectangle disappears almost immediately & all the links open as expected.

[Wilson]

Thank you! It was very sad watching helplessly as my two favorite addons fought with each other.

[70Chevelle]

Thank you for getting out a fix so quickly - I was having a rough time without my noscript - but I HAD to have my snaplinks -- so glad to have both back now

[Rdman]

The issue has reappeared. Everything past 1.9.7.9 acts just like before the fix.

[therube]

I've been meaning to revisit this topic too.

At times, what I have found with longer selected lists, is that only so many will open, others will be left unloaded.
(I noticed this well before the advent of ABE.)

Now that deals with SeaMonkey 1.1.17, in one particular Profile.
(I'll have to check that one a bit later.)

I never did fully verify that things were working correctly in this one particular Profile, & not too long ago, I noticed some problem there - but I don't know if it was actually ever resolved, hence "I've been meaning to revisit this topic too".


There were two issues that I had been seeing before.

First was the delay (synchronous) opening of links in Gecko 1.9.
Second was the fact that not all the selected links were firing.

It was this second issue which I observed recently in my SeaMonkey 1.1.17 Profile.

But I'll have to investigate further to see if it was actually resolved at some point in that Profile, & has returned more recently or if it has always been like that? And if the latter, then it may not even be a NoScript issue?

(Global installs <of NoScript> in SeaMonkey at times can make it difficult to adequately diagnose problems.)

[Giorgio Maone]

@rdman:
should be (re)fixed in 1.9.8.3.

[therube]

What I'm am seeing is NOT a NoScript issue.
I get inconsistent results regardless of NoScript & Gecko 1.8.1/1.9.0

Still seeing the issue in both SeaMonkey 1.1.17 & FF3.

Page with 30 links.

SeaMonkey 1.1.17, snaplinks (SeaMonkey version noted above)
FF3, snaplinks 102

Select all links, close, select close, ...

OOOPS, I 4GOT 2PUT IN 1.9.8.3 IN FF3 i'll try that first ..

Code: Select all

SeaMonkey & 1.9.8.1

24 open out of 30
 8 / 30
30 / 30
 8 /
 6 /
 8 /

SeaMonkey & 1.9.8.3

 8 /
30 /
14 /
 8 /
 
FF30, snaplinks 102, noscript 1.7.9.2

19 /
 8 /
 8 /

FF30, snaplinks 102, noscript 1.9.8.3

 7 /
30 /
 5 /
 7 /

FF30, disable noscript

 5 /
30 /
19 /
 8 /

FF30, uninstall noscript

14 /
 8 /
 8 /

disable .NET addon

26 /
 8 /
 
SeaMonkey 1.1.17, uninstall noscript

something less then 30 /
30 /
15 /
 5 /

I'm not done yet ... More shortly ...

OK, with pcqanda (link above) & SeaMonkey 1.1.17 & NoScript uninstalled, I'm getting consistent 30/30.
(pcqanda & not the site I was testing above <in quotes>)

pcqanda, SeaMonkey 1.1.17 (different Profile from above), NoScript 1.9.8.3 & I'm getting 30/30 consistently

my other <unamed> site, SeaMonkey 1.1.17, NoScript 1.9.8.3 & I'm just pulled an 8, then a 7, 9, & finally a 21.

pcqanda, FF30 (different 30 Profile <& different XP user> from above), NoScript 1.9.8.1 & I'm getting 30/30 consistently

my other <unamed> site, FF30, NoScript 1.9.8.1 & I'm just pulled a 21, 28, 8, & a 7.

i'm noticing no difference with FF30 & NoScript 1.9.8.1/3 & opening 30 links at pcqanda. i get 30/30 each time.
so my issue that I wanted to revisit is not (may not be) an issue. it is just something that is happening at a particular web site.

so ... can we conclude it is not a NoScript issue with that ?

I can email/pm you the unamed site if you want. Nothing special that I know of. Perhaps they have something in place to limit simultaneous opening links?