Errors in Web Console "Not allowed to enumerate cross origin

[rick]

Greetings & a happy new year

I've noticed the following issue:
in a fresh FF 17.0.1 profile
- install Noscript 2.6.4.2
- install Scriptish 0.1.8 or Greasemonkey 1.5
- and this script: YouTube Center

- Then visit eg. http://thefunnyvideoblog.com/
(Every script will be blocked by NoScript)

- Open Developer Toolbar (shift+F2)

You'll notice on the Web Console icon of the Developer Toolbar
that constant errors are coming for the forementioned script, all being

Error: Not allowed to enumerate cross origin objects @ youtubecenter.user.js:4407

This also causes a lot cpu usage.

Clicking "Allow all this page" in Noscript doesn't help.


The only solution is either to disable the forementioned script and reload the page
or to disable Noscript completely & restart FF.

Thank you.

[rick]

I've also made a report in the script's discussion page
Errors in Web Console "Not allowed to enumerate cross origin objects"
and it's developer suggests that

It seems like NoScript blocks YouTube Center from accessing a necessary YouTube function.

I also added a video capture of the problem there.

[Giorgio Maone]

- Then visit eg. http://thefunnyvideoblog.com/
(Every script will be blocked by NoScript)

It seems like NoScript blocks YouTube Center from accessing a necessary YouTube function.

Put the two together

If you don't enable scripting on the page, YouTube center won't be able to access "a necessary YouTube function" because that function has never been defined, since no script could run.
Did you try to allow scripting on that page?

[rick]

- Then visit eg. http://thefunnyvideoblog.com/
(Every script will be blocked by NoScript)

It seems like NoScript blocks YouTube Center from accessing a necessary YouTube function.

Put the two together

If you don't enable scripting on the page, YouTube center won't be able to access "a necessary YouTube function" because that function has never been defined, since no script could run.
Did you try to allow scripting on that page?

I write in my first post that:

Clicking "Allow all this page" in Noscript doesn't help.

The only solution is either to disable the forementioned script and reload the page
or to disable Noscript completely & restart FF.

[Giorgio Maone]

No idea, then.
It looks like a weird interaction between CAPS and Greasemonkey's wrappers (which would grant a bug report in Bugzilla), but I'm not sure about what it takes to produce a contrived test case.