[FIXED] Bookmarklet not working

[Ria]

Hi,

Since a few days (two or three days) my bookmarklet doesn't work anymore on a "forbidden" site with the latest Firefox nightly build.

My homepage (www.nu.nl) is a "forbidden" site because of an annoying cookiebar.
So after starting up the browser and reading my homepage I want to go to Gmail using this bookmarklet:
javascript:%20open('https://accounts.google.com/ServiceLogi ... ail/&hl=en');%20void%201

But it doesn't react.

When I click the bookmarklet on a whitelisted site, e.g. Google, there is no problem.
No big deal, but I thought I'd report it anyway.

Thanks for the attention,
Ria

[therube]

Confirmed.
But is it a NoScript issue or a Nightly issue?
I'm not sure if its working anywhere (i.e., even on an Allowed page)?
(At least in FF I wasn't sure. SeaMonkey is much easier to deal with.)

> a "forbidden" site

Appears all it needs to be is not allowed.

May or may not apply?
This was from FF, not seeing anything in SeaMonkey's Error Console.
(Though SeaMonkey Nightly is likewise affected.)

Code: Select all

"TypeError: Object.getPrototypeOf(...).open is undefined" JSURL.js:82
JSURL._run() JSURL.js:82
JSURL.load() JSURL.js:5
ns.executeJSURL() noscriptService.js:4424
noscriptBM.handleURLBarCommand/<() noscriptBM.js:36

[Ria]

Last "working" build I have in my possession is this one: https://hg.mozilla.org/mozilla-central/rev/cbe4f69c2e9c

[barbaz]

Confirmed.

Code: Select all

--
[08:36:57.680] TypeError: Object.getPrototypeOf(...).open is undefined @ chrome://noscript/content/JSURL.js:82

This is the related error message given by SeaMonkey (it's not in the Error Console because it's getting logged via the content document's console.error instead of something like Cu.reportError - why this design choice? ).

[Giorgio Maone]

Please check latest development build 2.6.8.29rc1, thanks.

[barbaz]

Fixed