Anthony Lieuallen wrote:
> No. Nothing was intentionally changed to make working scripts stop
> working.
>
> If you have a script that doesn't work, give us the script (a URL to
> it) and the URL for a page where it doesn't behave the way you expect.
> Explain what you expect, and what happens instead.
>
> Even better (and more likely to produce a fix / explanation): reduce
> the script to a minimal test case. Figure out which line of your
> script is running when the expected behavior fails, then start
> removing everything else (while not removing the failure case), and
> provide a link to the source for _that_ reduced case. (The
> http://gist.github.com/ site is great for that.)
>
Ok. Here it goes:
I have a script which created a link which, when clicked, changed a textbox.
Now, it produces a "Security Manager vetoed action" exception.
Simplified code:
var inputId = 'foo';
var value = 42;
var a = document.createElement('a');
a.appendChild( document.createTextNode( "Foo" ) );
a.href='#';
a.addEventListener( 'click', eval( 'function() {
document.getElementById("' + inputId + '").value = ' + value + '; }' ),
true );
document.body.appendChild( a );
Expected: input box foo gets set the value 42.
Result: Error: uncaught exception: [Exception... "Security Manager
vetoed action" nsresult: "0x80570027
(NS_ERROR_XPC_SECURITY_MANAGER_VETO)" location: "JS frame ::
http://127.0.0.1/greasemonkey.html :: anonymous :: line 0" data: no]
--
You received this message because you are subscribed to the Google Groups
"greasemonkey-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/greasemonkey-users?hl=en.
