HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
xiaoxiaoflood
firefox-scripts
JavaScript2021–2026
xiaoxiaoflood / firefox-scripts

firefox-scripts

userChromeJS / autoconfig.js and extensions

6Distinct people
11Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

userChromeJS / autoconfig.js and extensions

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2021-05-10 10:26:13 UTC to 2026-03-30 09:19:47 UTC.

012342021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC110
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

4 sources
UI customization is fortunately still alive in the wake of XUL extensions. A /r/firefoxcss mod has a wonderful collection of code snippets that they maintain, which you can browse here: https://mrotherguy.github.io/firefox-csshacks/ and they created a userChrome.js loader here: https://github.com/MrOtherGuy/fx-autoconfig My favorite customization repository is https://github.com/aminomancer/uc.css.js - which really tests the limits of what is and isn't possible with userChrome.css and .js. My favorite feature is the implementation vertical tabs, without the use of extensions. Some legacy extensions are maintained and can be found here: https://github.com/xiaoxiaoflood/firefox-scripts/tree/master... (although you will need to use xiaoxiaoflood's userChrome.js loader AFAIK). Honorable mention goes to the Firefox CSS Store, which can be foun
Read the rest
d here: https://trickypr.github.io/FirefoxCSS-Store.github.io/ Moving to WebExtensions was the logical choice for Firefox, technical/security reasons aside, as they are not alienating extension developers that target Chromium-based browsers. Yes, they alienated their own extension developers. Yes, they could've handled the transition better, and worked harder towards supporting some of the many APIs/functionalities that extension developers needed (or still need) for their extensions to work in the WebExtensions ecosystem. I myself was quite mad for a very long time at how they handled the switch, but I think overall it's been a success - my own personal feelings aside.
In Mozilla reaffirms that Firefox will continue to support current content blockers
Personally I've found https://github.com/xiaoxiaoflood/firefox-scripts/tree/master... very nice and almost indispensable – working versions of DownThemAll [1] and Norwell History Tools hacked to continue running on modern Firefox. [1] Yes, by now there's an official Webextension version of DownThemAll around again, too, but that's too much hobbled by the limitations of the Webextension API, i.e. can't download to outside of the official Downloads directory, can't intelligently/properly handle file name conflicts with already existing files [2], etc. [2] Most importantly, the Webextension API doesn't seem to have a "skip the download if the file already exists" option – it's only overwrite, rename the new download, or prompt, and Firefox doesn't even support the "prompt" option.
In A script to allow installing unsigned extensions on Firefox
And history is equally bad. Internally the browser stores each individual visit to a page, and also the full history trail in case you clicked on links, but the built-in UI only shows the last visit for each URL and nothing else. Additionally, when I do a history search, there's no way to jump from a search result back to the chronological view (though as soon as I open the result, the chronological view becomes useless anyway because it only shows the most recent visit, which after opening the page becomes of course "right now"). The problem is that quite often I might not remember the exact search terms to find a page again in my history, but can remember and find some other pages I know I visited beforehand/afterwards/etc. If I had the full chronological visit history (plus access to the link trail if necessary), I could just look thro
Read the rest
ugh that, but with the built-in UI that's not possible. Unfortunately, it seems that to this day, the best extension for solving this problem in Firefox predates the Webextensions cutoff and as usual the new Webextension API isn't quite set up for fully re-creating it because you can only query for visits by the exact URL, and so no modern add-on exists that is really a full replacement. Thankfully somebody hacked the original add-on to still work in modern Firefox, though of course it needs one of the Firefox varieties that are allowed to load arbitrary add-ons (https://github.com/xiaoxiaoflood/firefox-scripts/tree/master...).
In Ask HN: Why are bookmarks second class citizens in browsers?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.