![]() ![]() Then I have to manually bump the version every time I update the script to break the cache. Pop a new editor window with the bookmarklet and leave it open.Īll the meat and potatoes are in the main.js script that gets in.Open a script's editor page of Tampermonkey.I bound key with the macro for Sublime Text. Second, prepare a macro on Keyboard Maestro for copying and pasting to the popped editor window. Ideal would be to have a local webserver where you can control caching headers, so the browser doesn't cache at all, but I didn't bother because this worked well enough. I'd be surprised if Chrome was any different. I don't think I've seen a situation where the networking tab disagreed with Firefox caching (I'm using Firefox). In the network tab of the debugger you can see whether the resource is cached or not. What I've done is touch the files that I know will change, have a separate browser tab where that resource is open, clear the cache, then browser refresh. does send the Last-Modified header from which age_of_resource can be derived). (and my local webserver - twistd -n web -p 8000 -path. ![]() I can't find a reference to it at the moment, but I seem to believe that "the standard caching thing" is to cache things for some constant * age_of_resource. If the webserver doesn't send cache headers, it does the standard thing. - blog, documentation and discussion about Greasemonkey.: About caching: I think that standard browser caching is taking place.Try closing all tabs and load them fresh. Sometimes, usually on a portable device, it may look like the userscript manager is not working. ![]() The latest release of Greasemonkey does not currently accommodate this natively. Sometimes, when you use more than one userscript on the same web page, they may need to run in a particular order. Remember to reload the web page each time - userscripts normally only run when a web page loads. If it looks like you have a script problem and you have more than one script running on a web page, you can disable all of them in the Greasemonkey monkey menu, then re-enable them one by one, until you find the culprit. Remember to refresh any applicable windows and/or tabs. You can turn it on or off by clicking the monkey icon and toggling the "Greasemonkey is active" to a disabled state. If you think a userscript is causing problems, the easiest way to check is to switch off Greasemonkey, reload the web page, and see if the symptoms go away. Under each script menu entry in a sub-menu is the manual or automatic check for updates. Menu items here let you enable, disable or remove each installed script. If you click the Greasemonkey's monkey icon, currently there is a list of installed Userscripts. This will be a button or link to a file with a name that ends ".user.js"Īfter installing a userscript, you won't normally notice any further changes until you visit, or refresh, a website that it runs on. You just need to find the installation link for the script. Installing userscripts from other sources is a similar process. You may choose to install a Userscript in a disabled state as well. However if you ticked the "Open in editor after install completes" option the editor will open. You will need to reenable it from the Greasemonkey monkey icon and reinstall. Usually this means Greasemonkey is disabled. Sometimes, you may see just the source code of the userscript, rather than popping up the installation dialog straight away. If you only see a white boxed window try resizing it with the mouse grippy usually around the window border until the contents are visible as shown below: Click "Install" if you want to go ahead, and you should get a confirmation that the script has been installed. Navigate to the OpenUserJS page for the script, then click the blue "Install" button at the top of the page.Ī confirmation dialog box should pop up, showing you details about the script and the websites it can access. Once Greasemonkey is installed, installing userscripts from is simple. Once it has finished, you should see Greasemonkey's monkey icon at the top of the window, near the address bar. Firefox will show a warning and ask you to confirm adding the extension. This will show you the latest Greasemonkey version that will work with your version of Firefox.įrom the Greasemonkey page on AMO, click the blue "+ Add to Firefox" button to install the extension. To get userscripts going in Greasemonkey, first you have to install it from the Mozilla Add-Ons website, (AMO). It is the first extension to allow userscripts to be run in a web browser. Greasemonkey is a userscript manager for Firefox, originally written by Aaron Boodman and currently Firefox front-end and back-end maintained by Anthony Lieuallen and Johan Sundström. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |