4 ms·
Is the Chromium UserScripts page[1] out of date? Or are these still issues? Chromium does not support @require, @resource, unsafeWindow, GM_registerMenuCo
by pyre 17y ago
Is the Chromium UserScripts page[1] out of date? Or are these still issues?
Chromium does not support @require, @resource,
unsafeWindow, GM_registerMenuCommand, GM_setValue, or
GM_getValue.
A lot of scripts that I come across use `unsafeWindow`, `GM_setValue` and `GM_getValue.` It seems to be updated (since the last time I looked at it), since I believe it used to say that @exclude was not implemented, and now I don't even see a mention of it on the page (though I don't think I've come across a script that used @exclude).
[1]: http://dev.chromium.org/developers/design-documents/user-scripts http://dev.chromium.org/developers/design-documents/user-scr...
[UPDATE] This should shine some light on the topic: http://www.greasespot.net/2009/11/greasemonkey-api-usage.html http://www.greasespot.net/2009/11/greasemonkey-api-usage.htm...
- Semiapies 17y agoNone of my personal scripts (which all use @require or unsafeWindow) work on this. I've been meaning to convert them to Chrome extensions anyway, though.
- aboodman 17y agoMostly up to date, but I freshened some things.
- tung 17y agoA Chrome-modified script I'm looking at uses `localStorage.setItem(name, value)` and `localStorage.getItem(name)` to re-implement `GM_setValue` and `GM_getValue`. The author stores and recovers type info as the first character of the data.