[RESOLVED] Fx 28 breaks bookmarklet event listeners

[porl]

... and XHR and window.setTimeout() and dev tools, again! Same test cases as when Fx 27 broke them a month ago. Tested with NS 2.6.8.18rc1.

[therube]

Is it that it doesn't work in a New Tab, but will once a page has first loaded?

[porl]

Same as last time. Load a page, add an event listener in a bookmarklet or Scratchpad. Listener won't fire unless scripts are enabled for that domain.

[barbaz]

Confirmed in Gecko 28 with this testcase as URL bar typed/pasted JS:

Code: Select all

javascript:document.body.addEventListener("click", function(){alert("You clicked!");},false);void(0);

Also doesn't work from the Web Console.
Gecko 29 (SeaMonkey Aurora 20140317013001) doesn't seem affected.

[therube]

( Code: ... )
Are you sure that's correct?

[barbaz]

Yes, why?

[therube]

Well, at first I wasn't making it work.
And just now I did, accidentally.

But I do show that it works in FF28.
And SeaMonkey 2.26a2, Aurora.

With SeaMonkey you get a beep.
With FF, not.

It does not work on a about:newtab, about: ... type of "page", but maybe that's to be expected.

Oh, wait... FF had NoScript 2.6.8.11rc4 in it...

But I still see it working in FF28 with NoScript 2.6.8.18rc1.

[barbaz]

Heh, I didn't test Fx at all for reasons you can guess...
I was testing on a completely script-forbidden http page.

It never worked for me with any SeaMonkey on about: pages, even with scripts allowed and/or running the code from the Web Console instead of through NS, so I guess that is expected.

On the script-disabled http page, SeaMonkey 2.25 didn't fire the event listener at all, not even after running the test code from the Web Console or trying a new profile with only NoScript added (but no Web Console there...), so I would guess this is more likely a Gecko 28-specific bug than a NoScript bug or extension conflict.
@therube, what did you do that made it work, and on what page??

[Giorgio Maone]

Please check latest development build 2.6.8.18rc2, thanks.

[barbaz]

Seems fixed here, both URL bar JS and the Web Console work properly with my testcase in Gecko 28 now. Thanks a lot!

[porl]

I agree.

window.setTimeout/Interval() remain unavailable on script-disabled sites, but then I suspect that was already the case after last month's Firefox changes and it's not a very serious loss anyway.

Thanks Giorgio.

[barbaz]

window.setTimeout/Interval() remain unavailable on script-disabled sites

WFM, so it's probably another Gecko 28 bug..