> If you do that, you'll see in the error console:
>
> Error: Greasemonkey access violation: unsafeWindow cannot call GM_setValue.
I see. I guess you'd have to work around it somehow, like:
function cmd_manageUserScriptCommand(){
var $s = $('<script>');
$s[0].innerHTML = <![CDATA[(function({Utils}){
var mi = Utils.currentChromeWindow.document.querySelector(
'#userscript-commands-sb > menupopup > menuitem');
mi && mi._commandFunc();
})(Components.utils.import('resource://ubiquity/modules/utils.js', null))]]>;
$s.appendTo('body').remove();
}
Ubiquity scripts are indeed "unsafe," so we can't really complain =p
> I am curious about why
> Ubiquity scripts are "file:" urls and not "chrome:"
>From line 89-91 of sandboxfactory.js:
// We need to prefix any source code URI's with a known
// "protected" file URI so that XPConnect wrappers are implicitly
// made for them.
--
You received this message because you are subscribed to the Google Groups
"ubiquity-firefox" 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/ubiquity-firefox?hl=en.
