NoScript 2.1.0.4rc5 + Nightly 6.0a1 = hang at newegg.com

[alex-the-cat]

software config.:
NoScript 2.1.0.4rc5
Mozilla/5.0 (Windows NT 6.0; Win64; x64; rv:6.0a1) Gecko/20110509 Firefox/6.0a1

Step to reproduce:
1. go to newegg.com
2. click on any item
3. click Add to Cart
4. click View Shopping Cart
5. click on the check box on the left and click "Remove Selected"

Actual result:
browser hang

Expected result:
browser responds as usual.

note: you don't need to have a newegg account to test.

browser works as usual when it is restarted in safe mode with extensions disabled.

[dhouwn]

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a1) Gecko/20110509 Firefox/6.0a1, default settings, just newegg.com allowed, can't reproduce.

Your shopping cart is empty.

If you think this is an error, please click this link for suggestions.

[alex-the-cat]

FWIW, i'm using x64 nightly, not 32bit x86 build which you're using.

[dhouwn]

Indeed, that seems to make the difference, I can reproduce it with today's Windows x86-64 nightly. It's probably some Win64-specific bug NoScript is triggering which is probably not going to get fixed anytime soon since this platform is still not officially supported.

Maybe already reported in one of the following Firefox bug reports: https://bugzilla.mozilla.org/buglist.cg ... -net.ne.jp

[Giorgio Maone]

It seems to be caused by the "ab" surrogate (an anti-anti-adblocker surrogate).
If you disable it by setting the noscript.surrogate.ab.sources about:config preference to an empty string the problem should go away.
I'm not sure whether the window.watch() used in this surrogate to monitor the "ab" value is the specific cause: in fact, if it gets executed through a navigation bar scriptlet when the page is already loaded, it doesn't seem to trigger.

[alex-the-cat]

It seems to be caused by the "ab" surrogate (an anti-anti-adblocker surrogate).
If you disable it by setting the noscript.surrogate.ab.sources about:config preference to an empty string the problem should go away.
I'm not sure whether the window.watch() used in this surrogate to monitor the "ab" value is the specific cause: in fact, if it gets executed through a navigation bar scriptlet when the page is already loaded, it doesn't seem to trigger.

is this a permanent fix or just a temp. work-around? is there any consequences with this approach?

[Giorgio Maone]

is this a permanent fix or just a temp. work-around? is there any consequences with this approach?

A temp work-around.
This is surely a Firefox bug, but the current reproducible scenario is a bit too complex to make an easily fixable bug report.
So it will likely have a permanent work-around in next NoScript dev build, and hopefully a fix in a later Firefox Nightly.

[Giorgio Maone]

So it will likely have a permanent work-around in next NoScript dev build, and hopefully a fix in a later Firefox Nightly.

Actually it would seems this has been (unintentionally?) fixed in latest Nightly. Could you reset the preference to its original value and check whether it's actually OK for you without the work-around now?