50212 0 false 2009-09-12T21:51:28+02:00 50212 48956 15 integrate-wm-to-the-ff-add-ons-dialog 5 27038 open !medium #enhancement :big 2010-01-18T20:21:41+01:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/15 0.1a2 List installed userscripts in a "scripts" or "userscripts" tab in Firefox "Add-ons" dialog. This idea has also been mentioned on [GM issue 1012](http://github.com/greasemonkey/greasemonkey/issues#issue/1012/comment/45520). This is a major GUI update as the preferred script managing interface changes: userscripts present and behave as in the add-ons list. In other words, scripts are listed vertically, each one featuring: * an optional icon (see #15) * the script version (see #16) * the script description * an "options" button leading to the script config * a "disable" button * an "uninstall" button For a start, the "options" button may redirect to the current `manager.js` with the corresponding script selected. The next step would be to design a script-centric config interface. WM options could be pushed back into WM "Add-ons" tab "options" button. List installed userscripts in a "scripts" or "userscripts" tab in Firefox "Add-ons" dialog. This idea has also been mentioned on [GM issue 1012](http://github.com/greasemonkey/greasemonkey/issues#issue/1012/comment/45520). This is a major GUI update as the preferred script managing interface changes: userscripts present and behave as in the add-ons list. In other words, scripts are listed vertically, each one featuring: * an optional icon (see #15) * the script version (see #16) * the script description * an "options" button leading to the script config * a "disable" button * an "uninstall" button For a start, the "options" button may redirect to the current `manager.js` with the corresponding script selected. The next step would be to design a script-centric config interface. WM options could be pushed back into WM "Add-ons" tab "options" button. <div><p>List installed userscripts in a "scripts" or "userscripts" tab in Firefox "Add-ons" dialog.<br> This idea has also been mentioned on <a href= "http://github.com/greasemonkey/greasemonkey/issues#issue/1012/comment/45520"> GM issue 1012</a>.</p> <p>This is a major GUI update as the preferred script managing interface changes: userscripts present and behave as in the add-ons list. In other words, scripts are listed vertically, each one featuring:<br> * an optional icon (see <a href="/projects/27038/tickets/15" title= "Ticket #15">#15</a>) * the script version (see <a href= "/projects/27038/tickets/16" title="Ticket #16">#16</a>) * the script description * an "options" button leading to the script config * a "disable" button * an "uninstall" button</p> <p>For a start, the "options" button may redirect to the current <code>manager.js</code> with the corresponding script selected. The next step would be to design a script-centric config interface. WM options could be pushed back into WM "Add-ons" tab "options" button.</p></div> 50212 0 true 2010-01-08T00:14:47+01:00 81920 18 dumpster-newark-nj-908-313-9888 6 27038 invalid 2010-01-08T15:28:51+01:00 50212 Olivier Cornu dumpster Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/18 www.njwastedisposal.com www.njwastedisposal.com <div><p><a href= "http://www.njwastedisposal.com">www.njwastedisposal.com</a></p></div> 50212 0 false 2009-09-14T11:43:07+02:00 50212 48956 4 scripts-update-feature 1 27038 open !high #feature :big 2009-09-14T12:05:49+02:00 33943 Erik Vold Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/4 0.1a2 One of the most requested features out there: version checking and update of installed scripts. See: [GM#45](http://greasemonkey.devjavu.com/ticket/45) One of the most requested features out there: version checking and update of installed scripts. See: [GM#45](http://greasemonkey.devjavu.com/ticket/45) <div><p>One of the most requested features out there: version checking and update of installed scripts.</p> <p>See: <a href="http://greasemonkey.devjavu.com/ticket/45">GM#45</a></p></div> 50212 0 false 2009-09-12T22:08:07+02:00 50212 48956 16 support-for-version-header-tag 6 27038 open !medium #enhancement :trivial 2009-09-13T10:58:37+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/16 0.1a2 Parse, save and restore scripts `@version` string. This is a prerequisite to implementing script update (see #14) and displaying script version in the script list (see #15). Parse, save and restore scripts `@version` string. This is a prerequisite to implementing script update (see #14) and displaying script version in the script list (see #15). <div><p>Parse, save and restore scripts <code>@version</code> string.<br> This is a prerequisite to implementing script update (see <a href= "/projects/27038/tickets/14" title="Ticket #14">#14</a>) and displaying script version in the script list (see <a href= "/projects/27038/tickets/15" title="Ticket #15">#15</a>).</p></div> 50212 0 false 2009-09-12T22:42:35+02:00 50212 48956 17 specify-a-script-icon 7 27038 new !medium #enhancement :small 2009-09-13T03:22:44+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/17 0.1a2 Optional GUI feature, used among other things for "add-on" style userscript listing (see #15). Possible implementations include: * introduction of an `@icon` header tag * reserve the "icon" `@resource` name In both cases the target file would be downloaded into the script directory at install time. Optional GUI feature, used among other things for "add-on" style userscript listing (see #15). Possible implementations include: * introduction of an `@icon` header tag * reserve the "icon" `@resource` name In both cases the target file would be downloaded into the script directory at install time. <div><p>Optional GUI feature, used among other things for "add-on" style userscript listing (see <a href="/projects/27038/tickets/15" title= "Ticket #15">#15</a>).<br> Possible implementations include:</p> <ul> <li>introduction of an <code>@icon</code> header tag</li> <li>reserve the "icon" <code>@resource</code> name</li> </ul> <p>In both cases the target file would be downloaded into the script directory at install time.</p></div> 50212 0 false 2009-09-12T19:34:42+02:00 50212 14 object-storage-support-for-gm_setvaluegm_getvalue 6 27038 new !low #enhancement :small 2009-09-13T03:16:45+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/14 So far `GM_setValue` and `GM_getValue` only support integers, boolean and strings. It would be nice if they supported objects as well, in order to load/save a bunch of values (the object properties) at once. As i see it, a preferences _branch_ would be named after the key parameter, with object properties saved as `key.propertyName` values of this branch. Example code: @@@ javascript // ==UserScript== // @name script // @namespace namespace // ==/UserScript== var object = { aBoolean = true, aInt = 1, aString = "string" } GM_setValue("key", object); @@@ `about:config` would thus contain the following: @@@ webmonkey.scriptvals.namespace/name.key.aBoolean = true webmonkey.scriptvals.namespace/name.key.aInt = 1 webmonkey.scriptvals.namespace/name.key.aString = string @@@ `GM_getValue("key")` would perform the opposite operation. Notes: * Such preferences values would also be reachable individually using the standard syntax. * The mechanism might be extended to support object properties as well, as long as there is no reference loops (same as JSON). So far `GM_setValue` and `GM_getValue` only support integers, boolean and strings. It would be nice if they supported objects as well, in order to load/save a bunch of values (the object properties) at once. As i see it, a preferences _branch_ would be named after the key parameter, with object properties saved as `key.propertyName` values of this branch. Example code: @@@ javascript // ==UserScript== // @name script // @namespace namespace // ==/UserScript== var object = { aBoolean = true, aInt = 1, aString = "string" } GM_setValue("key", object); @@@ `about:config` would thus contain the following: @@@ webmonkey.scriptvals.namespace/name.key.aBoolean = true webmonkey.scriptvals.namespace/name.key.aInt = 1 webmonkey.scriptvals.namespace/name.key.aString = string @@@ `GM_getValue("key")` would perform the opposite operation. Notes: * Such preferences values would also be reachable individually using the standard syntax. * The mechanism might be extended to support object properties as well, as long as there is no reference loops (same as JSON). <div><p>So far <code>GM_setValue</code> and <code>GM_getValue</code> only support integers, boolean and strings. It would be nice if they supported objects as well, in order to load/save a bunch of values (the object properties) at once.<br> As i see it, a preferences <em>branch</em> would be named after the key parameter, with object properties saved as <code>key.propertyName</code> values of this branch.</p> <p>Example code:<br></p> <pre> <code class="javascript">// ==UserScript== // @name script // @namespace namespace // ==/UserScript== var object = {<br> <br> </code> </pre> <pre> <code class="javascript"><code>aBoolean = true, aInt = 1, aString = &amp;quot;string&amp;quot;</code></code> </pre> <pre> <br> } GM_setValue("key", object); </pre> <code>about:config</code> would thus contain the following: <pre> <code>webmonkey.scriptvals.namespace/name.key.aBoolean = true webmonkey.scriptvals.namespace/name.key.aInt = 1 webmonkey.scriptvals.namespace/name.key.aString = string</code> </pre> <code>GM_getValue("key")</code> would perform the opposite operation. <p>Notes:<br> * Such preferences values would also be reachable individually using the standard syntax. * The mechanism might be extended to support object properties as well, as long as there is no reference loops (same as JSON).</p></div> 50212 0 true 2009-03-15T12:49:36+01:00 50212 8 api-is-unsafely-added-to-the-sandbox 5 27038 invalid !high #enhancement :small 2009-09-02T11:40:48+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/8 We protect scripts by wrapping them inside a function (currently, unless `@unwrap` is used). We should protect the API similarly, otherwise it is accessible from the hostile environment after `unsafeWindow` usage. See: [GM#225](http://greasemonkey.devjavu.com/ticket/225) We protect scripts by wrapping them inside a function (currently, unless `@unwrap` is used). We should protect the API similarly, otherwise it is accessible from the hostile environment after `unsafeWindow` usage. See: [GM#225](http://greasemonkey.devjavu.com/ticket/225) <div><p>We protect scripts by wrapping them inside a function (currently, unless <code>@unwrap</code> is used).<br> We should protect the API similarly, otherwise it is accessible from the hostile environment after <code>unsafeWindow</code> usage.</p> <p>See: <a href="http://greasemonkey.devjavu.com/ticket/225">GM#225</a></p></div> 50212 0 false 2009-03-23T14:46:25+01:00 50212 48956 10 gm_-api-functions-should-be-wrapped-into-a-gm-object 4 27038 open !low #enhancement :trivial 2009-09-02T11:36:25+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/10 0.1a2 The `GM_*` functions should be renamed as `*` and wrapped into a `GM` object. For example, `GM_log` would become `GM.log`. For backward compatibility purpose, legacy naming should be temporarily conserved while being deprecated. The `GM_*` functions should be renamed as `*` and wrapped into a `GM` object. For example, `GM_log` would become `GM.log`. For backward compatibility purpose, legacy naming should be temporarily conserved while being deprecated. <div><p>The <code>GM_*</code> functions should be renamed as <code>*</code> and wrapped into a <code>GM</code> object. For example, <code>GM_log</code> would become <code>GM.log</code>.</p> <p>For backward compatibility purpose, legacy naming should be temporarily conserved while being deprecated.</p></div> 50212 0 false 2009-03-27T15:19:48+01:00 50212 48956 11 add-proper-code-documentation 3 27038 open !medium #enhancement :big 2009-08-30T20:55:44+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/11 0.1a2 The code could use better documentation, preferably in JSDoc format. The code could use better documentation, preferably in JSDoc format. <div><p>The code could use better documentation, preferably in JSDoc format.</p></div> 50212 0 false 2009-08-24T20:45:48+02:00 50212 48956 12 refactor-the-code 2 27038 open !high #enhancement :big 2009-08-29T19:18:50+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/12 0.1a2 The code and its structure need some cleanup... The code and its structure need some cleanup... <div><p>The code and its structure need some cleanup...</p></div> 50212 0 true 2009-08-21T13:44:10+02:00 50212 2009-08-29T00:00:00+02:00 33915 13 firebug-support-for-script-debugging 9 27038 resolved !high #enhancement :small 2009-08-22T15:32:15+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/13 0.1a1 It currently isn't possible to debug scripts using the great Firebug debugger, although that would be particularly helpful. Let's fix that! It currently isn't possible to debug scripts using the great Firebug debugger, although that would be particularly helpful. Let's fix that! <div><p>It currently isn't possible to debug scripts using the great Firebug debugger, although that would be particularly helpful. Let's fix that!</p></div> 50212 0 true 2009-03-15T01:18:43+01:00 50212 5 webmonkey-icon-wastes-horizontal-space 2 27038 resolved !low #annoyance :small 2009-06-05T14:28:18+02:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/5 *"Greasemonkey is currently the only icon on my statusbar which wastes an unacceptable amount of space. I'm attaching an image which illustrates how it currently looks (top) and how it should look (bottom)."* See: [GM#173](http://greasemonkey.devjavu.com/ticket/173) *"Greasemonkey is currently the only icon on my statusbar which wastes an unacceptable amount of space. I'm attaching an image which illustrates how it currently looks (top) and how it should look (bottom)."* See: [GM#173](http://greasemonkey.devjavu.com/ticket/173) <div><p><em>"Greasemonkey is currently the only icon on my statusbar which wastes an unacceptable amount of space. I'm attaching an image which illustrates how it currently looks (top) and how it should look (bottom)."</em></p> <p>See: <a href="http://greasemonkey.devjavu.com/ticket/173">GM#173</a></p></div> 50212 0 true 2009-03-23T14:39:11+01:00 50212 2009-08-29T00:00:00+02:00 33915 9 failing-unwrapped-scripts-are-executed-twice 6 27038 resolved !medium #bug :trivial 2009-03-24T11:36:31+01:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/9 0.1a1 For backward compatibility purposes, following script wrapping mess in previous GM releases, we're left with the following code: $$$ if (!script.unwrap) scriptSrc = "(function(){"+ scriptSrc +"})()"; if (!this.evalInSandbox(scriptSrc, url, sandbox, script) && script.unwrap) this.evalInSandbox("(function(){"+ scriptSrc +"})()", url, sandbox, script); // wrap anyway on early return $$$ In other words, if an unwrapped script fails to execute properly, it is wrapped and executed again. This might result in a page being (at least partly) modified twice. Scripts failing because of `@unwrap` issues should be fixed, not "hot-patched" like this. For backward compatibility purposes, following script wrapping mess in previous GM releases, we're left with the following code: $$$ if (!script.unwrap) scriptSrc = "(function(){"+ scriptSrc +"})()"; if (!this.evalInSandbox(scriptSrc, url, sandbox, script) && script.unwrap) this.evalInSandbox("(function(){"+ scriptSrc +"})()", url, sandbox, script); // wrap anyway on early return $$$ In other words, if an unwrapped script fails to execute properly, it is wrapped and executed again. This might result in a page being (at least partly) modified twice. Scripts failing because of `@unwrap` issues should be fixed, not "hot-patched" like this. <div><p>For backward compatibility purposes, following script wrapping mess in previous GM releases, we're left with the following code: $$$</p> <pre> <code> if (!script.unwrap) scriptSrc = "(function(){"+ scriptSrc +"})()"; if (!this.evalInSandbox(scriptSrc, url, sandbox, script) &amp;&amp; script.unwrap) this.evalInSandbox("(function(){"+ scriptSrc +"})()", url, sandbox, script); // wrap anyway on early return </code> </pre> <p>$$$ In other words, if an unwrapped script fails to execute properly, it is wrapped and executed again. This might result in a page being (at least partly) modified twice.</p> <p>Scripts failing because of <code>@unwrap</code> issues should be fixed, not "hot-patched" like this.</p></div> 50212 0 true 2009-03-15T03:08:33+01:00 50212 2009-08-29T00:00:00+02:00 33915 7 gm_xmlhttprequest-bypass-cache 4 27038 resolved !medium #enhancement :trivial 2009-03-15T03:20:21+01:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/7 0.1a1 [GM#157](http://greasemonkey.devjavu.com/ticket/157): An extra option could be added to `GM_xmlhttpRequest` to bypass the cache. Mozilla provides the code: @@@ request = new XMLHttpRequest(); request.channel.loadFlags |= Components.interfaces.nsIRequest.LOAD_BYPASS_CACHE; @@@ ...which will allow privileged callers to bypass the cache. [GM#157](http://greasemonkey.devjavu.com/ticket/157): An extra option could be added to `GM_xmlhttpRequest` to bypass the cache. Mozilla provides the code: @@@ request = new XMLHttpRequest(); request.channel.loadFlags |= Components.interfaces.nsIRequest.LOAD_BYPASS_CACHE; @@@ ...which will allow privileged callers to bypass the cache. <div><p><a href="http://greasemonkey.devjavu.com/ticket/157">GM#157</a>:</p> <p>An extra option could be added to <code>GM_xmlhttpRequest</code> to bypass the cache.</p> <p>Mozilla provides the code:</p> <pre><code> request = new XMLHttpRequest(); request.channel.loadFlags |= Components.interfaces.nsIRequest.LOAD_BYPASS_CACHE; </code></pre> <p>...which will allow privileged callers to bypass the cache.</p></div> 50212 0 true 2009-03-15T00:54:08+01:00 50212 2009-08-29T00:00:00+02:00 33915 3 add-binary-support-to-gm_xmlhttprequest 3 27038 resolved !medium #enhancement :trivial 2009-03-15T02:53:23+01:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/3 0.1a1 Mozilla introduced binary file support in `XMLHttpRequest` starting from Firefox 3.0, through the `sendAsBinary()` method. `GM_xmlhttpRequest` should be updated to support it as well. See: [GM#228](http://greasemonkey.devjavu.com/ticket/228) Mozilla introduced binary file support in `XMLHttpRequest` starting from Firefox 3.0, through the `sendAsBinary()` method. `GM_xmlhttpRequest` should be updated to support it as well. See: [GM#228](http://greasemonkey.devjavu.com/ticket/228) <div><p>Mozilla introduced binary file support in <code>XMLHttpRequest</code> starting from Firefox 3.0, through the <code>sendAsBinary()</code> method.<br> <code>GM_xmlhttpRequest</code> should be updated to support it as well.</p> <p>See: <a href="http://greasemonkey.devjavu.com/ticket/228">GM#228</a></p></div> 50212 0 true 2009-03-15T00:46:30+01:00 50212 2009-08-29T00:00:00+02:00 33915 2 gm_xmlhttprequest-doesnt-report-connection-errors 2 27038 resolved !medium #bug :trivial 2009-03-15T02:13:36+01:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/2 0.1a1 `GM_xmlhttpRequest` doesn't call `onerror` callback when some connection error occurs (cannot find address in DNS, server refuses connections, timeout, etc). See: [GM#100](http://greasemonkey.devjavu.com/ticket/100) `GM_xmlhttpRequest` doesn't call `onerror` callback when some connection error occurs (cannot find address in DNS, server refuses connections, timeout, etc). See: [GM#100](http://greasemonkey.devjavu.com/ticket/100) <div><p><code>GM_xmlhttpRequest</code> doesn't call <code>onerror</code> callback when some connection error occurs (cannot find address in DNS, server refuses connections, timeout, etc).</p> <p>See: <a href="http://greasemonkey.devjavu.com/ticket/100">GM#100</a></p></div> 50212 0 false 2009-03-15T01:26:24+01:00 50212 6 cant-scroll-to-the-bottom-of-the-scripts-list 3 27038 new !high #bug :small 2009-03-15T02:03:14+01:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/6 When the list of scripts is longer than the scripts box is high, it is not possible to scroll all the way to the bottom. Reproducible by resizing the manage dialog. See: [GM#24](http://greasemonkey.devjavu.com/ticket/24) When the list of scripts is longer than the scripts box is high, it is not possible to scroll all the way to the bottom. Reproducible by resizing the manage dialog. See: [GM#24](http://greasemonkey.devjavu.com/ticket/24) <div><p>When the list of scripts is longer than the scripts box is high, it is not possible to scroll all the way to the bottom.<br> Reproducible by resizing the manage dialog.</p> <p>See: <a href="http://greasemonkey.devjavu.com/ticket/24">GM#24</a></p></div> 50212 0 true 2009-03-14T23:29:04+01:00 50212 2009-08-29T00:00:00+02:00 33915 1 wm-logs-an-error-if-firebug-is-not-installed 1 27038 resolved !low #annoyance :trivial 2009-03-15T01:59:14+01:00 50212 Olivier Cornu Olivier Cornu Olivier Cornu http://ocornu.lighthouseapp.com/projects/27038/tickets/1 0.1a1 See: http://greasemonkey.devjavu.com/ticket/232 See: http://greasemonkey.devjavu.com/ticket/232 <div><p>See: <a href="http://greasemonkey.devjavu.com/ticket/232">http://greasemonkey.devjavu.com/...</a></p></div>