Is Mozilla just messing with us or is there a purpose behind all this

• uc.css.js

  215 304 7.7 JavaScript

  A dark indigo CSS theme for Firefox and a large collection of privileged scripts to add new buttons, menus, and behaviors and eliminate nuisances. The theme is similar to other userChrome stylesheets, but it's intended for use with an autoconfig loader like fx-autoconfig, since it uses JavaScript to implement its more functional features.

Bug looks kinda dead. I hope they go through with that though. The bookmark tag parameter is completely unnecessary and redundant now that custom search engines exist. Haven't used it in years personally, but I use custom search engines and urlbar addons on a daily basis. There are ways it could be improved but I went ahead and implemented them myself a while back. I agree they're not super convenient to create without addons (I can understand if many users were not even aware they could make them) but sounds like this feature request would ship with a change to the about:preferences search engines interface that would make custom engines much more accessible.

• Zotero-Dark-Theme

  8 707 0.0 CSS

  userChrome.css file for a Zotero dark theme. Suggestions for improvements are welcome.

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• firefox-csshacks

  669 2,950 8.7 CSS

  Collection of userstyles affecting the browser

This one works: https://github.com/MrOtherGuy/firefox-csshacks/blob/master/chrome/tabs_on_bottom.css

• userChrome.js

  16 434 7.2 JavaScript

can you give a specific example of how they've been "slowly crippling customizability" since the migration to webextensions? from where I'm standing, the ability to customize the browser is same as it ever was. I make several scripts a month that modify the firefox UI more heavily than most addons from 2006 ever did. and so do several other people like Alice0775 and xiaoxiaoflood. the modules that are now called "addons" may not be able to hack the browser much like the modules that used to be called "addons," but you can do all the same shit with javascript and XPCOM today that you could back then using a very slightly different method.

• firefox-scripts

  131 922 1.6 JavaScript

  userChromeJS / autoconfig.js and extensions

can you give a specific example of how they've been "slowly crippling customizability" since the migration to webextensions? from where I'm standing, the ability to customize the browser is same as it ever was. I make several scripts a month that modify the firefox UI more heavily than most addons from 2006 ever did. and so do several other people like Alice0775 and xiaoxiaoflood. the modules that are now called "addons" may not be able to hack the browser much like the modules that used to be called "addons," but you can do all the same shit with javascript and XPCOM today that you could back then using a very slightly different method.

• fx-autoconfig

  101 152 8.1 JavaScript

  Load custom javascript in browser context

All you need to do is download an autoconfig loader, make a file in the new "JS" folder called blockOneOffKeyNav.uc.js, and paste this inside it:

Suggest a related project