[Greasemonkey] GM_Import and Caching
Gareth Andrew
freega at freegarethandrew.org
Thu Jan 5 19:21:41 EST 2006
Hi Tom,
Thanks for the heads-up, if you are happy with source-hacking you can
fix this by adding
persist.persistFlags =
Components.interfaces.nsIWebBrowserPersist.PERSIST_FLAGS_BYPASS_CACHE;
to scriptdownloader.js line 197.
I'm glad to see you are enjoying the new feature; one word of warning
though is that GM_Import is not yet a supported feature. It may take
some time before this actually makes it into a released version of
greasemonkey, and the syntax could change between now and then. I only
say this because I myself have a couple of gm scripts which I would have
liked to release but can't since their dependant on GM_Import
Gareth.
On Thu, 2006-01-05 at 02:43 -0500, Tom Tobin wrote:
> I've been starting to develop userscripts using the soon-to-come
> GM_Import functionality, and I've found things *much* easier due to
> the ability to modularize my code. One issue I've run into, however,
> is that the @import rule apparently pulls from the cache if possible;
> this is a problem if a library has recently been updated, as Firefox
> will favor the cache over the remote copy. The only workaround I've
> found so far is to empty the cache before reinstalling the userscript;
> is there an easier solution I'm missing?
> _______________________________________________
> Greasemonkey mailing list
> Greasemonkey at mozdev.org
> http://mozdev.org/mailman/listinfo/greasemonkey
More information about the Greasemonkey
mailing list