PUBLIC MARKS from decembre with tag greasemonkey

Unified Script Injector (usi) is a new Firefox add-on that has been designed to provide users of Firefox for Android with means to run userscripts. While Firefox desktop users have some choice when it comes to adding userscript support to their browser, Greasemonkey and the newly released Tampermonkey come to mind, none of these option appear to work on Firefox for Android. The new Firefox add-on usi changes that by adding support for a wide variety of usrescripts. The author notes on the official add-on page that the add-on supports some Greasemonkey functions but not all of them. What this means is that you may encounter userscripts that don't work yet when you install them with the help of the browser extension.

After a certain amount of time the user is inactive (default is 10 minutes) this script redirects a tab to the homepage. This appears to be useful for Kiosk browsing environments – after someone leaves the computer the next person can start at the home page again.

This user script helps you to: skip countdown ads or continue pages. prevent ad pop-up windows. It CANNOT help you to solve reCAPTCHAs. Forked from RedirectionHelper written by SuYS.

I have an huge Style , impossible (for me) to compress more to publish here ... I want find a way to convert it , automatically if it is possible, into an greasemonkey .

FIR 57 - ADDON - uBO/webext works best with Firefox 57 and above, and with multi-process enabled. There are many reports of people experiencing issues with some web sites, or images not loading, etc. Turns out many of these are a result of using some legacy extensions along uBO/webext. For instance, Reek's AAK in GreaseMonkey has been causing issues with images not loading. If you experience such issue, you will have to disable all your legacy extensions and see if this fixes your issue. If so, then you will have to re-enable your legacy extensions one by one to find the one(s) causing the problem. Those legacy extensions can cause multi-process to be disabled in your browser, and apparently when multi-process is disabled, this can cause many cases of page load failure.

Working and updated forum....

What? The Greasespot Wiki will be updated to explain Greasemonkey 4 in detail. Until then, here's a quick summary. First, there is only an embedded editor. Browser Extensions have no access to the file system, so you can no longer author user scripts in your familiar text editor. There is only one object provided to user scripts now, named GM. It has several properties. One of them is info – the equivalent of the old GM_info. There are also several methods of this object: getResourceUrl, deleteValue/getValue/listValues/setValue, xmlHttpRequest. To use these methods you still need @grant, and use the new name, e.g.: // @grant GM.setValue The new form has a dot, where the old form has an underscore. You may specify both @grants, if you'd like to be compatible with Greasemonkey 4 and other user script engines at the same time. As of today, there is no support for: GM_log (use console.log), GM_addStyle, GM_registerMenuCommand, nor GM_getResourceText.

I'm the administrator of userstyles.org. I want to start offering my styles to Greasemonkey (and similar) users. For applicable styles on userstyles.org, just plunk "/style.user.js" at the end of the URL. (For example, http://userstyles.org/style/show/242/style.user.js ). Not all styles on the site can be converted into user scripts. For example, those affecting chrome wouldn't work. Those styles will return a 404 if you try to open their styles. I'd like some feedback on the format I'm using. Is the code the best it can be, are there problems with meta-data, etc. Thanks.

Greasemonkey 4 is available as an alpha version currently. Compatibility is restricted to Firefox 56 and earlier howeve

Greasemonkey 4 is changing how it runs user scripts. Many user scripts will continue to run as expected, but this will break some scripts. If you rely on such scripts, you might want to install Violentmonkey or Tampermonkey, both of which provide compatibility for existing scripts. If you'd prefer to stick with Greasemonkey, you'll need to wait for the script to be updated to be compatible. Find the original author of your script, and ask them to update for Greasemonkey 4 compatibility. Referencing this post may help.

checkForBadJavascripts: This is a utility function, meant to be used inside a Greasemonkey script that has the "@run-at document-start" directive set. It Checks for and deletes or replaces specific "scrip" tags.

Thanks to some awesome answers in other threads, I learned how to: load jQuery and jQuery-UI in a bookmarklet load a CSS into a bookmarklet using jQuery create a DIV in a bookmarklet using jQuery create jQuery UI dialog (external link) and I could manage to combine all four things into a single script which works both as a BookMarklet and as a GreaseMonkey script, which is absolutely awesome.

For use on production websites with any amount of traffic. Files are served via MaxCDN's super fast global CDN. No traffic limits or throttling. It's best to use a specific tag or commit hash in the URL (not a branch). Files are cached permanently after the first request. The catch: this is a free service, so there are no uptime or support guarantees.

vent from happening or replace it with my own code

use Greasemonkey to modify the script or to insert another script just after it to override the function

The implement of @run-at document-start greatly extent what userscript capable range. This snippet is one of the example show how to interfere the original script before they run, instead of stay away until the DOM is ready ( DOMContentloaded event fired ).

On Firefox Greasemonkey, you can do that with the stupefyingly brilliant (^_^) checkForBadJavascripts utility

Forum: MooTools - Forum d'entraide sur le framework MooTools.

You can make MPIV work with more sites by adding your own host rules. You don't need to edit the source code for this. Instead, you paste the rule into MPIV's settings dialog which is accessible from your script manager's toolbar icon menu, e g. "User Script Commands" → "Set up Mouseover Popup Image Viewer" for Greasemonkey users.

In Greasemonkey tutorial, I have covered how to write Greasemonkey user scripts. After this tutorial,you will be able to write user-scripts for Greasemonkey. Topics covered: GreaseMonkey Installation Hello World Example Adding a Button Reading/Modifying HTML content Loading External Scripts.

If you have issues with the Greasemonkey extension itself, please use the greasemonkey-users ("questions about creating or installing user scripts")

Here are a few Firefox extensions that I consider essential for any Firefox installation.

This is working code in case someone has the same question in the future:

Replacing links to images is not too hard to do. However, I recommend that you keep the link but display the picture inside it. This is so you can click through if something goes wrong. For example, that sample page you gave has most of the linked images on a dead site. Other linked images only look like they point to images or might be blocked for "hot linking". To make the code robust and easy, we use jQuery and waitForKeyElements. Here is a complete working script that delinks the payload image-links on that sample site: