InformAction Forums

It sounds like there must be some script on those domains that is causing trouble (maybe waiting for something else that NoScript blocks?), and ABP is probably blocking the troublemaker.

If we can identify exactly what does it, then ABE or a surrogate script could fix it.

@Thrawn: I agree, but even so, that doesn't explain why the hang is longer with NS 2.6.8.31 than it is with 2.6.8.29...

Admittedly, I have insufficient technical knowledge to make an accurate assessment, but your assessment does sound reasonable and logical; ABP is blocking something on the problematic pages.

It's easy to view the list of "blockable items" in ABP, but I honestly don't know what to look for specifically.

Just to make sure we haven't all overlooked somthing and this isn't some change on Yahoo's end, does downgrading NS back to 2.6.8.29 help at all?
https://addons.mozilla.org/addon/noscript/versions

Yes, indeed it does help; downgrading to 2.6.8.29 seems to resolve the issue (I also tried 2.6.28 with similar results). There are some slower page loads, but nowhere near as slow and unbearable as in the latest build. Also, absolutely no hangs on any of the pages I loaded.

Just wanted to report that the new development build, 2.6.8.32rc1, appears to have resolved the "hanging issue" that was prevalent in 2.6.8.31 without resorting to using ABP.

Page load times vary; some Yahoo pages still load slowly, but more on the order of 2.6.8.29 rather than 2.6.8.31 and, again, I haven't seen any instances where my browser appears to hang.

Check that.....2.6.8.32rc1 still borks some Yahoo pages. I reverted to 2.6.8.28 and all is well. Hope this gets resolved soon.

If Giorgio doesn't have anything to add soon, can you check http://noscript.net/feed?t=a and let us know what is the latest NoScript dev build that does not cause issues with Yahoo?

Well, after some further testing, I can only conclude that Yahoo changed something that induced the slow loading of certain pages with NoScript installed and configured in various ways. The rationale therefore is that some pages load slowly no matter which version of NoScript I use, even 2.6.8.28 which never caused any issues for me previously.

I have, I believe, narrowed the issue down to articles on Yahoo's main web site that contain "Yahoo comments". For example, regardless of which NoScript version is installed, blocking yahoo.com and yimg.com results in almost instantaneous loading of pages but then the comments (i.e., articles with "View Comments" at the end) do not load. Articles that do not contain "Yahoo comments" seem to load promptly and properly, regardless.

Anyone can test this scenario merely by clicking articles on Yahoo's main page. If yahoo.com and yimg.com are blocked, pages will load quickly while if they are allowed, pages with "View Comments" at the end of the articles will load slowly and occasionally result in a hang depending on the NoScript version installed.

I have exactly the same problem as the other users, but with some differences.
I using Firefox and Seamonkey on Linux Debian. When I open a new tab from yahoo main page, my browser hangs for about one or two minutes.
The top command shows that firefox uses more than 100% of the CPU during all the time of the hang.
I have always had adblock installed and it doesn't change anything for me.
I have downgraded noscript to 2.6.8.29 and it doesn"t change anything.

@Stefchiff: That sounds like a completely different issue - if it was a Yahoo script causing that hang, you would get a slow script dialog prompting whether to stop the script or not within 30 seconds. Please do Standard Diagnostic and let us know the results.

I've never said my problem was a slow script from yahoo. The problem comes exclusively from noscript : if I deactivate noscript the pages load normaly.
But I would like to continue using noscript.

StefChiff, create a new, clean Profile.
Install only NoScript.
Does Yahoo continue to react with the same delay on page opening?

I have created a new profile and installed only noscript, the last release, and I get exactly the same problem, it means that this problem is exclusively caused by noscript no ?

StefChiff wrote:I have created a new profile and installed only noscript, the last release, and I get exactly the same problem, it means that this problem is exclusively caused by noscript no ?

Generally yes, that's correct.

Does it still fail even if you Allow Scripts Globally?
If so, when it fails, anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post all the remaining messages)

Also what Adblock Plus subscriptions are you using?