PUBLIC MARKS from decembre with tag FIR57

This extension makes easier to use more profiles in Firefox and Thunderbird. This extension will not be compatible with Firefox versions > 52, due to the changes decided by Mozilla in extensions support with Firefox. Alternative : In firefox 57 or quantum you open a new tab, write about:profiles and manages your profile

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.

How to enable Firefox WebExtensions on Mozilla websites (in https://www.ghacks.net/2017/10/27/how-to-enable-firefox-webextensions-on-mozilla-websites/): - Load about:config in the Firefox web browser. - You can run a search for just to make sure it does not exist: privacy.resistFingerprinting.block_mozAddonManager. It does not in the most recent Firefox Nightly builds at the time of writing. - Right-click in the part of the window that lists the preferences, and select New > Boolean from the context menu. - Name the new Boolean value: privacy.resistFingerprinting.block_mozAddonManager. - Set its value to true.

f you have friends that want to start with building WebExtensions show them this link https://vimeo.com/2402821339 Most people start with “Hello World” web sites when they want to learn Front End stuff. This is boring. Building an WebExtension as the first web project is sooo totally awesome! :smiley: I choose to sign it as unlisted WebExtension since lots of people don’t know it’s possible and if you are a n00b and want to share your extension in 5 minutes regardless of how useless it is, an unlisted web extension is better than a listed one.

userChrome.css is a style sheet with special importance to Firefox. The rules in userChrome.css are applied to the user interface, and can override nearly every built-in style rule. Unfortunately, you cannot use userChrome.css to change the functional operation of Firefox; that's what extensions are for. Creating a userChrome.css file and adding style rules allows you to make changes to fonts and colors, hide unnecessary items, adjust spacing, and make other changes to the appearance of Firefox. The following examples illustrate the wide range of effects you can create, either by creating your own style recipes, or building on the work of CSS wizards sharing their talents on the web.

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.