Article updates – 31-Oct-2018

The Firefox Configuration Guide for Privacy Freaks and Performance Buffs was heavily updated again. The biggest change was the re-introduction of uMatrix in addition to uBlock Origin. I dropped the former quite a while back thinking that uBO could handle everything sufficiently enough, but that’s not the case. Much other information was overhauled as well.

The Firefox Tweaks and Fixes and Styles and Things article was also updated again. I added a couple things including a warning about using the sidebar CSS. If you happen to be using that code, or any style that auto-opens/closes the sidebar, please read the warning.

Looking Glass: The next ‘bright idea’ from Mozilla (updated)

Back in the day, Firefox was sort of a hackers power browser that fit a niche market. It was probably the most tweakable mainstream web browser on the planet for both geeks and average users alike. Although it is still highly customizable, it has become less so since Mozilla decided to terminate support for so-called “legacy” add-ons and replace them with WebExtensions of the same type as used by Google Chrome. Matter of fact, Firefox has become a Google Chrome clone as far as i’m concerned and some of us — a core Firefox audience that liked running something different and something that wasn’t ‘Googlized’ — didn’t want anything to do with Google, much less their Chrome web browser.

In its [not so] slow, steady decline and separation from its core values, Mozilla has dumbed-down Firefox to the point where it is hardly recognizable and changed its add-on API several times, thus forcing developers to rewrite their code in order to comply with yet another new standard. The developer of the much loved Search WP extension had this to say:

I’d love to support Firefox 57 (with all my extensions) but

1) Webextensions are just *too* limited. You simply can’t do anything useful with them until somebody adds an API just for you. It already starts with the most basic functionality of SearchWP: there does not seem to be a way to modify the search bar.

2) Mozilla ruthlessly breaking all existing extensions on purpose and removing customization possibilities with every new version of Firefox made me loose trust in the foundation and the browser itself – I’m not willing to spend my spare time on a project that has set a course that goes against everything Firefox once stood for.

And the stupidity continues…

For some time Mozilla has been packaging extensions with Firefox in the form of system add-ons, or “features” as Mozilla calls them. Not only is the option to uninstall these add-ons absent from the user interface, but most people aren’t even aware they exist since they’re hidden from the Add-Ons panel (if you want to know more about system add-ons and how to remove them, read the article, Firefox Configuration Guide for Privacy Freaks and Performance Buffs).

In its latest burst of stupidity, Mozilla is now installing yet another add-on without consulting users, but this time, to their undeserved credit, they have made it removable apparently. ‘Looking Glass‘ appears to be some kind of metrics collection add-on disguised as an augmented reality game created by the PUG Experience Group, whoever the hell they are, and it is part of a series of “Shield Studies” conducted by Mozilla. To see what studies Mozilla has foisted upon you that you didn’t agree to, enter about:studies in the address bar and then about:preferences#privacy to opt out. Better yet, stop using the Mozilla version of Firefox altogether.

Of course adding this unwanted crap to Firefox isn’t the worst of it. A while back, Mozilla decided that it needed to jump on the “fake news” bandwagon with its newly created Mozilla Information Trust Initiative in order to steer you away from sources of information that the multi-million dollar Mozilla Foundation decides are not suitable for your consumption.

I no longer suggest using Firefox, at least not the version distributed by Mozilla. If you want Firefox with the privacy disrespecting garbage removed, consider using Waterfox, which is a more privacy-centric, 64 bit fork of Firefox that will apparently continue to support XUL (legacy) extensions in addition to the newer WebExtensions. Some of the features of Waterfox are:

  • Disabled Encrypted Media Extensions (EME)
  • Removed Pocket
  • Removed Telemetry
  • Removed data collection
  • Removed startup profiling
  • Allow running of all 64-Bit NPAPI plugins
  • Allow running of unsigned extensions
  • Removal of Sponsored Tiles on New Tab Page

UPDATE: Mozilla apologizes.

On 18-Dec., after many users complained about the inclusion of the Looking Glass add-on, for which almost nothing was known at the time it was distributed, Mozilla published an apology, moved the add-on to the Mozilla add-on repository and published the source code. The post opened with the following nonsensical statement which raises more questions than it answers:

Over the course of the year Firefox has enjoyed a growing relationship with the Mr. Robot television show and, as part of this relationship, we developed an unpaid collaboration to engage our users and viewers of the show in a new way: Fans could use Firefox to solve a puzzle as part of the alternate reality game (ARG) associated with the show.

Does this sound remotely like anything that should be included in an internet web browser? What is the nature of Mozilla’s relationship with Mr. Robot? We already know that Mozilla has a habit of adding unnecessary functionality through its inclusion of 3rd party services for monetary gain and using its relationships with many privacy destroying corporations, such as Google, to monetize necessary functionality, yet they packaged the Looking Glass add-on with Firefox for no other reason other than, what? They like Mr. Robot? They wanted to make sure you weren’t bored by giving you a game to play? Utter bullshit. And why wasn’t the source code published before the add-on was shipped? And how do we know that the published code is identical to the unpublished code?

The rollout did not meet the standards to which we hold ourselves causing concern that was surfaced through our Firefox community.

Yes it did because Mozilla sacrificed its standards long ago. The only reason they published this apology is because enough users complained.

We received feedback regarding the transparency of the rollout and the processes that govern our auto-install mechanism for add-ons. In response we immediately started our internal review, […]

Good thing most users have no clue about the several system add-ons and “features” that ship with Firefox which are forcefully installed, activated, not easily uninstalled, and are used to collect data. Of course we know that no internal review will be performed to address this glaring privacy issue.

We’re sorry for the confusion and for letting down members of our community. While there was no intention or mechanism to collect or share your data or private information […]

When one considers exactly what Mozilla defines as “user data” and “private information”, one realizes how hollow this misleading claim rings. If they’re so concerned about their users, why aren’t they concerned about the data that is still being collected by the forcefully installed system add-ons of which users are largely unaware? Why aren’t these add-ons removed and placed in the add-on repository?


Firefox Tweaks and Fixes and Styles and Things

Customize the appearance of the Firefox web browser and its derivatives without using add-ons.


Following is a collection of tweaks and fixes for the Mozilla Firefox web browser and its derivatives. Keep an eye out for changes as i tend to update this stuff fairly often.

For the non-techies, here are brief descriptions of some of the Firefox configuration files which are in play in this article:

  • prefs.js: This is the primary Firefox configuration file that controls much of how the browser works. This file exists in the root of your Firefox profile directory. The contents of this file can be viewed and edited by entering about:config in the address bar, however you should typically not edit this file unless it’s only to test something. All of your custom preferences should be placed in a user.js file (or a user-overrides.js file if you’re using the ‘ghacks’ user.js).
  • user.js: This file does not exist until you create it in the root of your Firefox profile directory. Any preferences that you wish to change in prefs.js or about:config that are not available in the Firefox options interface, and which you want to preserve across Firefox updates or resets, should be entered in this file.
  • userChrome.css: This file does not exist until the you create it in the chrome folder of your Firefox profile. This file is used to modify the appearance of virtually any element of the Firefox user interface (UI).
  • userContent.css: This file does not exist until the you create it in the chrome folder of your Firefox profile. This file can be used to modify the appearance and behavior of web pages, however i would recommend using the Stylus add-on instead because it makes working with CSS much easier.

If you need help with Cascading Style Sheets (CSS), selectors and what parameters they can take, see the CSS Introduction and CSS Reference documents at

Changing how Firefox looks


Since Mozilla removed support for the older XUL/XPCOM add-ons in favor of WebExtensions, the much loved Classic Theme Restorer add-on won’t work with Firefox version 57 or newer. The developer of CTR is still very active in maintaining the CSS code that was used in the add-on however and you can find it in the CustomCSSforFx GitHub repository. Using the new code, we can continue to tweak the crap out of Firefox, though it requires a bit more elbow grease. I’ve removed several of the CSS tweaks i had here in favor of the CustomCSSforFx code because it covers so much ground and saves a lot of time without adding too much overhead. You can also hide Firefox context menu items with CustomCSSforFx or you could roll your own styles and dump them in userChrome.css.

Instructions for implementing the CustomCSSforFx code is on the page i linked to, though i might recommend implementing it a little differently if you already have code in your userChrome.css or userContent.css that you want to keep. The method i use keeps my custom code separate from the CustomCSSforFx code which makes updating the CustomCSSforFx stuff a little easier. It also allows to quickly troubleshoot problems that might arise because you can just comment out a single @import line to easily eliminate large chunks of code. Here’s what my userChrome.css contains:

/* @namespace url(""); /**/

/* Aris-t2/CustomCSSforFx ( */
@import "./custom/aris-t2/userChrome.css"; /**/

/* all my other custom code below */

Notice that the @namespace line is commented out. You need to do the same, else some of the tweaks in the CustomCSSforFx code might not work. To understand why you don’t need the @namespace line, even though you may have read that you do, and why it can cause styles to break, read Adding Style Recipes to userChrome.css.

As you saw above, the userChrome.css in my /chrome folder is a rather bare-bones affair in which i use @import to link to the CustomCSSforFx files and all my other CSS files that reside in sub-folders of /chrome. Here’s what the directory hierarchy looks like if you’re confused:


And here’s what my userContent.css file looks like, which just points to the userContent.css file contained with the CustomCSSforFx package:

/* Aris-t2/CustomCSSforFx ( */

@import "./custom/aris-t2/userContent.css"; /**/

/* all my other custom code below */

Once you’ve got the files in place, it’s just a matter of editing the userChrome.css and userContent.css files to suit your needs. The instructions are contained in the files. It will take a while to go through it all, but i suggest doing so because some tweaks are OS and Firefox version specific. Aris updates the CustomCSSforFx code quite often, so you might want to watch the repository for changes.

When it’s time to update the styles, things get a little tricky if you want to avoid having to sift through the userChrome.css and userContent.css files all over again. One solution by ‘petsam’ called ‘Pretty Firefox‘ attempts to automate the process as much as possible. I haven’t used his script so i can’t comment on it, suffice to say that any effort to automate the updating of CustomCSSforFx is appreciated i’m sure. The method i use requires a little work to set up and a familiarity with regular expressions, but handling updates is super easy.

    1. In the same folder that i dump the CustomCSSforFx files, i create 2 additional files: userChrome_RegEx.txt and userContent_RegEx.txt.
    2. As i go through the userChrome.css and userContent.css files to enable/disable styles, i copy the file paths of every uncommented line to the appropriate .txt file. For example, if i uncomment @import "./css/buttons/icons_colorized.css"; /**/ and @import "./css/appbutton/appbutton_popup_more_icons.css"; /**/ in userChrome.css, i copy the following to userChrome_RegEx.txt. Note that i don’t leave any spaces between the strings and i include the quotes:
    3. When i’m finished adding the file paths, i prepend ^/\* @import ( and append ) to the string, then replace every dot with \.and "" with "|". Here’s an example:
      ^/\* @import ("\./css/buttons/icons_colorized\.css"|"\./css/appbutton/appbutton_popup_more_icons\.css"

If you have a lot of options enabled your string could get really long and that’s OK. When i’m done with userChrome.css, i do the same for userContent.css.

When it comes time to update the CustomCSSforFx files, we can use some regular expressions to make the job really quick. For both the userChrome.css and userContent.css files:

  1. find: ^@import
    replace: /* @import
  2. find: (the expression from the appropriate RegEx text file)
    replace: @import \1

The only negative to my method that i’m aware of is that you won’t be aware of any new options added to the CustomCSSforFx code and so once in a while it’s a good idea to look it over.

Dark Fox

Firefox ships with a few default themes and one of them is the ‘Dark’ theme. To activate it, right-click on an empty part of the tab bar or the navigation tool bar, or click the ‘Customize’ menu item in the Hamburger menu. At the bottom of the ‘Customize Firefox’ tab you’ll see a ‘Themes’ button. Click it and select the ‘Dark’ option.

Shadowfox is another alternative.

Auto-open/hide the sidebar

This CSS tweak allows to open the sidebar by simply moving your mouse cursor to the extreme left of the browser window and close it by moving your mouse off of the sidebar. You many not want to use this if you don’t usually keep Firefox maximized. There are two issues with this style: Because the position of the sidebar is set to ‘relative’, it shares the same space as the page you’re browsing and so it narrows the page by 1 pixel. May not sound like anything worth a complaint, but it bothers me. Problem is, i’ve been unable to get the sidebar to display properly if i set its position to ‘fixed’. Also, in the original code that i found (stole), the author removed the sidebar header and i wanted to keep it. This creates the second issue in that, if you change the contents of the sidebar using the drop-down menu in the header, the sidebar will collapse and must be reopened.

WARNING: Because the sidebar is essentially always open, but hidden, if an item in the sidebar has focus and you press, for instance, the delete key even when the sidebar is hidden, the sidebar item that has focus will be deleted! I stopped using this style myself for this reason, and also because it will no longer be possible to drag stuff (like a bookmark) into the sidebar, however i decided to keep the code here in the event others aren’t bothered by these issues.

Don’t forget to set --sbarwidth to your desired value.

* Contributor(s): img2tab
:root {
    --sbarwidth: 420px; /* set width you want the sidebar to be when it's open */
#sidebar-header {
    border-bottom: none !important;
.sidebar-header, #sidebar-header {
    font-weight: normal !important;
    color: white !important; /* comment out for a light theme /**/
#sidebar-box {
    overflow-x: hidden;
    min-width: 0px;
    max-width: 0px;
    position: relative;
    padding-left: 5px !important;
    padding-right: 0 !important;
    background-color: #2e2e2e !important; /* comment out for a light theme /**/
    border-right: 1px solid; /* width of the border which opens the sidebar /**/
    cursor: pointer;
    transition: all 0.1s ease 0.15s; /* first number is transition time and second is open/close delay time */
#sidebar-box #sidebar {
    min-width: var(--sbarwidth);
    max-width: var(--sbarwidth);
    padding-right: 10px;
#sidebar-box ~ #sidebar-splitter {
    display: none;
.sidebar-placesTree {
    color: white !important; /* comment out for a light theme /**/

/* bookmark panel item spacing - optional */
.sidebar-placesTree treechildren::-moz-tree-row {
    margin: -2px;

Adjust vertical space between the bookmark items

This will change the vertical space between your bookmarks in the sidebar. You can use CustomCSSforFx for this, or copy the following code to your userChrome.css. Change the -2 to whatever suits you.

/* bookmark panel item spacing */
.sidebar-placesTree treechildren::-moz-tree-row {
    margin: -2px;

Styling the link target/network status tooltip

The link/status tooltip is the text that appears in the lower left or right of the browser viewport when you hover over a hyperlink or when there is certain network activity. Some people (me!) find the link tooltip really annoying because it can cover part of a webpage and get in your way. This style will have the following effects:

  • move the hyperlink tooltip to the top of the browser, overlaying the tab bar (adjustable)
  • make the hyperlink tooltip the full width of the browser (almost)
  • make the hyperlink tooltip background transparent black and the text white
  • center the hyperlink tooltip text
  • leave the network status tooltip on the bottom of the viewport, but make the background transparent white and the text black
/* move the hyperlink tool-tip to the top of the browser */
#statuspanel[type="overLink"] {
  position: fixed;
  top: 26px; /* adjust as necessary */
  left: 0;
  width: 100%;
  z-index: 3;
  text-align: center;

/* style the hyperlink tool-tip */
#statuspanel[type="overLink"] #statuspanel-label {
  background-color: #0000008c !important;
  color: white !important;
  height: 27px !important; /* adjust as necessary */

/* style the status tool-tip */
#statuspanel[type="status"] #statuspanel-label {
  background-color: #ffffff9c !important;
  color: black !important;

/* make sure the the status tooltip is hidden when it's inactive */
#statuspanel[inactive] #statuspanel-label {
  display: none !important

Changing how Firefox works

In addition to the smooth scrolling tweak below, see the articles, Firefox Configuration Guide for Privacy Freaks and Performance Buffs and The Firefox Privacy Guide For Dummies!, as well as my user-overrides.js.

Smooth scrolling

Smooth scrolling is apparently enabled by default in Firefox, but i don’t care for the way it works. If you want to try my settings, copy the smooth scroll code from my user-overrides.js file on my GitLab repository (scroll down until you find the line === 12BYTES.ORG SMOOTH SCROLLING ===).

Making the user interface (UI) bigger on small displays

The Firefox UI consists of several parts including toolbars, the tab bar and the viewport where web pages are displayed. If you’re working on a high resolution, small format display, such as a laptop with a 1080p screen, everything may look too small. From the Firefox preferences you can easily enlarge the font sizes used by web pages. By the way, when you change font sizes in the “Fonts & Colors” section of the Firefox preferences, make sure to set the same sizes for “Other Writing Systems” in addition to your language (which is Latin if you read English). If the toolbar buttons, address bar text and other parts of the Firefox UI are also too small, adjusting font sizes will do nothing to enlarge them, so here’s what you can do:

  1. Enter about:config in the address bar
  2. In the search box, enter layout.css.devPixelsPerPx
  3. Set the value of this preference to whatever decimal number (0.9, 1.1, 1.2, etc.) you want until the toolbars and icons are a comfortable size (the change will take effect immediately). Don’t use too large of a number. What is too large? I don’t know, but once you get close to 2 you might notice very strange issues with the UI. I use a value of 1.3 for a 17 in., 1080p display.

This will also enlarge all web pages and so you may want to adjust your desired font sizes in Firefox’s options, both for your preferred language and ‘Other Writing Systems’.

If you use the developer tools you can enlarge all of that using the devtools.toolbox.zoomValue preference.

When you’re done, you should put those preferences in a user.js file.

Changing how websites look or work

The styles below can be used in a userChrome.css file, but i would recommend using the Stylus add-on mentioned earlier. If you dump them in userChrome.css you’ll need to make some changes so that they affect only the websites you want them to affect.

Making the interwebs dark

Many of us who have been staring at computer monitors too damn long cannot tolerate bright displays. White web pages with dark text feels like looking at the sun, which is one reason why i use a dark theme for this website. A lot of people seem to have this problem and there are many solutions. In the case of Firefox, there are quite a few add-ons that can darken the web and they use various methods to do so. The simplest ones invert the colors which is a dumb method for a couple reasons, one of them being that this can make dark pages look bright. To see my preferred extension for darkening the web, see Firefox Extensions – My Picks.

Allow text selection/copying

In a silly effort to prevent copying text, some website admins will try to prevent you from selecting it, or at least make it appear that you can’t select it by changing the selection color to the same color as the background. This tweak will often solve the problem.

Name: [global] allow text selection
Applies to: Everything

/* override CSS preventing text selection */
* {
    -moz-user-select: text !important;
    user-select: text !important

Copying/pasting text without formatting

Sometimes you may want to copy text from a website and paste it without the HTML markup. While i’m not aware of any way to accomplish this without an extension, you may be able to do the next best thing by using Ctrl+Shift+V to paste instead of Ctrl+V. This works for me on Windows and Linux, however i’ve had some feedback that indicates it does not work in all cases. If you have a problem, look for a global or application specific Ctrl+Shift+V hotkey setting and consider deleting or changing it.

Copying text from hyperlinks

Copying the text of a hyperlink can be a hassle, that is until you press the Alt key. Just press and hold your Alt key while dragging the cursor to highlight the text you want to copy. You can even copy text from the middle of a hyperlink this way. There are extensions that can do this too, but the less you install, the better.

Display website content hidden by JavaScript

I’m noticing more and more websites using JavaScript and a DIV layer to hide page content until the page is fully loaded (Engadget employs this stupidity). While this CSS tweak will not work in every case, it will work in some, including many more than those listed as examples. Note also that it may occasionally break how a website is displayed, though i haven’t had any trouble with that as far as i know.

Name: [global] anti-JS - display html
Applies to: Everything

 * display html hidden by JS
 * note that some styles may break some websites
/* ex: */
html {
    display: unset;

body {
    /* generic */
    opacity: 1 !important;
    /* ex: */
    visibility: unset;

/* ex: */
body > #mask {
    display: none;

/* ex: */
body > .content-loader {
    display: none;

/* ex: */
body > .loader-wrapper {
    display: none;

/* ex: */
body #preloader {
    display: none;

/* ex: */
body #loader-wrapper {
    display: none;

/* ex: */
body > #load {
    display: none;

/* ex: */
body > #qLoverlay {
    display: none;

/* ex: */
body > .preloader {
    display: none;

/* generic */
body .site {
    opacity: 1 !important;

Display images hidden by JavaScript

Many websites will not display images unless you enable JavaScript. While this tweak is certainly not a universal fix (many websites use a lazy-load script that requires JavaScript), it will work in some cases.

Name: [global] anti-js - display images
Applies to: Everything

img img {
    opacity: 1 !important;
    filter: none;
/* ex: */
.loading-circle {
    display: none !important;

Display YouTube videos hidden by JavaScript

Many websites will not display embedded YouTube videos unless you enable JavaScript. This will make the video display without having to enable JS in some instances, however JS must still be enabled for

Name: [global] anti-JS - display YouTube player
Applies to: Everything

/* ex: */
div.player-unavailable {
    display: none !important;

Normalizing fonts

I like fonts styles and sizes to look somewhat uniform across websites, plus there are privacy issues for some websites that use 3rd party fonts, such as the “free” fonts that Google provides (hint: when something is “free”, you are likely the product). There are various ways to achieve this, but here’s the method i suggest:

  1. In Firefox preferences, find the ‘Fonts & Colors’ options and click the ‘Advanced’ button.
  2. If you read English, select ‘Latin’ in the combination control, else select your preferred language.
  3. Set the ‘Proportional’, ‘Monospace’ and ‘Minimum’ font styles and sizes and remember your choices. I set the ‘Proportional’ option to ‘Sans Serif’ and all the other options to one of the sans fonts (not serif or sans-serif fonts)
  4. In the combination control, select ‘Other Writing Systems’ and set the preferences to the same values as in the last step.
  5. Disable the option, ‘Allow pages to choose their own fonts’.
  6. Install the Toggle Fonts add-on by Manuel Reimer.

Fonts should now look much more uniform across all websites and if you don’t like the way a particular website looks, just click the Toggle Fonts toolbar button which will allow the website to specify its own fonts. Another option is to use something like the ReFont add-on, but that’s a bulkier solution that introduces other issues and so i don’t really recommend it, especially if you use uBlock.

Lastly, if you use uBlock, read the part about fonts in the Firefox Configuration Guide for Privacy Freaks and Performance Buffs.

Redirecting this to that

Using an extension like Redirector, you can automatically redirect one resource to another. Here i’m just providing some generic examples that you should be able to adapt depending on which redirect extension you’re using.

Bypass YouTube short links

Redirect shortened YouTube video links ( to, thus avoiding the unnecessary middleman.

  • Name: YouTube short link bypass
  • Include pattern: https://youtu\.be/([a-zA-Z0-9]*)
  • Redirect to:$1
  • Pattern type: Regular expression

Turn off LiveLeak safe mode

This will disable safe mode for LiveLeak videos without having to log-on.

  • Name: LiveLeak disable safe mode
  • Include pattern: https?:\/\/www\.liveleak\.com\/view\?i=(.+?)(?!&safe_mode=off)*$
  • Redirect to:\?i=$1&safe_mode=off
  • Pattern type: Regular expression

Disable BitChute channel sensitivity filter

If you don’t mind getting your ‘fee-fees’ hurt.

  • Name: BitChute disable channel sensitivity filter
  • Include pattern: https:\/\/www\.bitchute\.com\/channel\/([^/]*)
  • Redirect to:$1/?showall=1
  • Pattern type: Regular expression

Redirect BitChute embed links to video page

Sometimes people (here’s looking at you James Corbett!) post links to a BitChte video that loads the embed page instead of the video page. Annoying! Here’s how to redirect those links to the video page.

  • Name: BitChute embed link to video page
  • Include pattern: https:\/\/(?:www\.)?bitchute\.com\/embed\/([^/]*)
  • Redirect to:$1/
  • Pattern type: Regular expression

Fixing stuff that’s busted

Firefox doesn’t remember its window size after restart

If you maximize the Firefox window and then close it, it may not reopen in a maximized state as one might expect. This annoyance can be caused when the preference privacy.resistFingerprinting is set to true (as it should be). This preference does a number of things to make it harder for websites to fingerprint your browser and one of them is to set a generic window size. If this bothers you, try the Maximize All Windows (Minimalist Version) add-on by ‘ericchase’, but know that your browser will be much easier to fingerprint and track if JavaScript is enabled since the browser viewport size is far more unique than something like its User-Agent string for example.

Webpages don’t fill the entire viewport (inner window)

When privacy.resistFingerprinting is set to true (as it should be), web content may not fill the entire viewport (aka ‘inner window’, the part of the browser that displays webpages). This behavior is controlled by a hidden preference, privacy.resistFingerprinting.letterboxing, that does not exist by default and which can be set to true or false. While this may be an annoyance, understand that disabling this setting is likely to greatly increase fingerprint entropy (make your browser much easier to identify). If you still want to disable this protection, you can create a the preference in about:config (boolean) or add it to your user.js or user-overrides.js and set it to false.

Dark text on a dark background

If you run Linux with a dark GTK theme, it can happen that text labels and other controls can have a very dark background color while the text itself is also dark, making these areas unreadable. Mozilla has known about this for 18 years! The solution that partially worked for me (thanks to Moritz Kammerer and Evan Klitzke) was simply to add a new string preference to my user.js file and give it a value matching the name of a light colored GTK theme installed on my system, then restart Firefox:

user_pref("widget.content.gtk-theme-override", "Adwaita:light");

You can replace Adwaita:light with the name of any other light colored GTK theme, such as Breeze. I also found that omitting :light works as well and the string value is not case sensitive, so just plain adwaita will work.

If you still have problems with dark text on a dark background in other areas or controls, try these styles in a userContent.css file:

/* prevent  black text on black background for text input controls on some about: pages */
@-moz-document url-prefix(chrome://mozapps/content/extensions/extensions.xul), url-prefix(about:addons) {
    input, textarea {
        color: black !important;
        background: white !important;

/* prevent black text on black background for context menu in some about: pages */
@-moz-document url-prefix(chrome://mozapps/content/extensions/extensions.xul), url-prefix(about:addons),
url-prefix(chrome://mozapps/content/extensions/extensions.xul), url-prefix(about:config),
url-prefix(chrome://mozapps/content/extensions/extensions.xul), url-prefix(about:downloads) {
    menupopup, panel {
        color: white !important;

/* prevent black text on black background for buttons in some about: pages */
@-moz-document url-prefix(chrome://mozapps/content/extensions/extensions.xul), url-prefix(about:webrtc) {
    button {
        color: white !important;

Disappearing tool-bar and/or Start Panel icons

This seems to happen when duplicating my Firefox profile without first exiting Firefox, so you can possibly avoid this problem altogether by exiting the browser before creating a copy of your profile. If you still have issues however, load about:config in the address bar and in the search box enter extensions.databaseSchema, then right-click this preference and click ‘Reset’. Restart Firefox and your icons may reappear. Why this works i have no idea because, in my case, the value of extensions.databaseSchema returns to the same value as it was previously.

Troubleshooting problems with add-ons

If you notice a problem that you think may be related to an add-on, there are some simple steps you can take to troubleshoot the issue before contacting the developer. In my experience problems with add-ons are usually a result of a conflict with 1) a setting in prefs.js, 2) a setting in user.js, 3) another add-on, or 4) something in userchrome.css or usercontent.css. Whatever the case, the following information should help you to troubleshoot the issue.

If you suspect an add-on is giving you trouble…

  1. Backup your Firefox profile! Load about:profiles if you don’t know where it’s located, then exit Firefox and find your profile folder in your file manager and press Ctrl+C and Ctrl+V to make a copy. When you are prompted for a new name, just add -bak to the existing name.
  2. If you have any custom configuration files, such as a user.js, userChrome.css or userContent.css, rename them (add .bak to the existing name), then start Firefox and verify whether the problem still exists.
    1. If the problem no longer exists, go to the Troubleshooting preferences section below.
    2. If the problem still exists, continue with the next step.
  3. Start Firefox and load about:support by entering that in the address bar, then click ‘Restart with Add-ons Disabled’.
  4. Open the about:addons page and, one by one, enable each add-on until the problem reappears, at which point you will know which add-on is causing the problem.
  5. Go to and install a fresh copy of the problematic add-on and verify that the problem is still exists.
    1. If the problem no longer exists, your finished.
    2. If the problem still exists, submit a bug report to the add-on developer (see below).

How to submit a bug report like a pro

If you have a problem with an add-on, or with Firefox itself, you need to be able provide the developer with enough pertinent information so they are able to reproduce it, else they may simply ignore you. Comments like “it don’t work” are useless to a developer and you shouldn’t be surprised if they ridicule you for submitting such non-descriptive tripe. When describing the problem, be as brief as possible while still including every necessary detail. Here’s a template which you can use for bug reports:

Operating system [name]
Firefox [version]
Add-on (if relevant) [name] [version] [link]
Affected webpage (if relevant) [URL]

Brief but accurate description of the problem...

What, if anything, you tried to solve the problem...

Precise steps to reproduce the problem...

With that information in hand, you need to find where the developer wants you to submit bug reports. If it’s a buggy add-on, load up about:addons and see if there’s a support link in the information for it by clicking the ‘More’ button. If there isn’t, go to the add-on page at and see if the developer provides a link to a support website (preferred!) or at least an email address. If they provide neither, then you’re left with no other choice than to post your issue in the add-on comments, but do this only when no other option is available and don’t down-vote the add-on. Lastly, make sure the title of your submission is descriptive of the problem. Titles like “bro its so borked LOL” are meaningless to a developer who is now more likely to disregard your issue since you just exposed yourself as a 12 year old slab-fondler.

Troubleshooting Firefox preferences

Problems resulting from settings in your prefs.js file can manifest in different ways, from breaking desired Firefox or extension functionality to causing web pages to not work properly or failing to load at all. Following is one method of troubleshooting preference issues for those who are not comfortable using the Firefox console, or where the console did not provide useful information. Though tedious, this method almost always works. You should have a decent code editor with syntax highlighting for editing the Firefox prefs.js file, such as Kate (Linux), or PSPad or Notepad++ (Windows).

  1. Start Firefox and enter about:profiles in the address bar, then load that page.
  2. Create a new profile for testing, naming it something like ‘__testing__’ so it cannot be easily confused with your default profile.
  3. In the ‘Root Directory’ row, click the ‘Open Directory’ button for both your original and your testing profiles to open the folders in your file browser.
  4. Start Firefox using your testing profile. it may ask which profile to load since you now have more than one, but if it doesn’t then load about:profiles again and select the option to open your testing profile in a new window. Nowverify that the problem still exists, then exit Firefox.
  5. If the problem no longer exists, continue with the next step. If it does, troubleshooting the problem is beyond the scope of this troubleshooter, suffice to say that it may due to an add-on or custom CSS in your Firefox /chrome folder if you have one, etc..
  6. With Firefox closed, copy (Ctrl+C) the prefs.js file in your original profile folder and paste it (Ctrl+V) in your testing profile folder, overwriting the existing one.
  7. Repeat step 4. If the problem reappears you have verified it is due to a preference in the prefs.js file. If it does not, then it is beyond the scope of this troubleshooter.
  8. With Firefox closed, open the prefs.js file from your testing profile in your code editor and select roughly half of the contents of the file, making sure your selection starts at the beginning of a line and ends at the end of a line in order to avoid further problems. Next, cut (Ctrl+X) the selection (don’t just delete it!) and save the file. If your editor complains it is important that you ignore the warning and force the save. If it automatically reloads the file, you will need to disable that behavior in its settings.
  9. Keep repeating steps 4 and 8 until the issue disappears, at which point you know the preference causing the problem is stored in your clipboard (the last section you cut from prefs.js).
  10. Select all of the contents in prefs.js (Ctrl+A) and delete (not cut!) the selection, then paste (Ctrl+V) to paste the contents of your clipboard and save the file, again being sure to force the save if your code editor complains.
  11. Again, continue repeating steps 4 and 8 until you have narrowed down the problem to a single preference at which point you know what preference is causing the problem.
  12. Once the problem is isolated to a single preference, you can then copy it to your user.js file (or user-overrides.js file if you have one) in your default profile and change it’s value there after which you can verify the problem was solved by running Firefox with your default profile.

Once you have solved the problem in your default profile, you can delete your testing profile from about:profiles or from the profile loading prompt when Firefox starts.

More Firefox stuff

Other articles i’ve written about Firefox and its derivatives can be found on the Everything Firefox page.

For more CSS tweaks, see:

General Firefox stuff:

YAMR (Yet Another Mozilla Rant) – Battling “fake news”

This is it folks. This is a ‘rotten cherry on the top of the stinking cake’ moment with a big fat pit right in the middle of it.

I recently learned that the multi-million dollar Mozilla corporation has decided that i (and you) are idiots; that we are incapable of analyzing news stories in order to determine whether they are creditable; that we should be reading the Wall Street Journal and the New York Times and the like to get our “news”. And so Mozilla has decided that it is they, the developers of a freaking web browser, that should step in to help steer us back on the right track by saving us from … FAKE NEWS!

Yes, on 8 August, 2017, the Mozilla foundation launched their incarnation of the Great Firewall of China by deciding to combat “fake news” via The Mozilla Information Trust Initiative, aka MITI. And what news does the Mozilla Information Trust Initiative consider “fake news”? Well, apparently any news that doesn’t originate from a mainstream source:

Imagine this: Two news articles are shared simultaneously online.

The first is a deeply reported and thoroughly fact checked story from a credible news-gathering organization. Perhaps Le Monde, the Wall Street Journal, or Süddeutsche Zeitung.

THE WALL STREET JOURNAL!?!? “… a deeply reported and thoroughly fact checked story …“. Are You Kidding Me Right Now!

Let’s just have a quick look at the track record of the Wall Street Journal which, by the way, is essentially as biased and corrupt as any other mainstream government/corporate mouthpiece:

20 Reasons Not to Trust the Journal Editorial Page | FAIR (1-Sep-1995)

When Anita Hill took a polygraph test to try to substantiate her charges of sexual harassment against Clarence Thomas, the Wall Street Journal attacked her in an editorial (10/15/91) titled “Credibility Gulch�: “Lie detector tests are so unreliable they are rarely allowed as evidence in court.�

But just eight months later (6/9/92), when the Journal argued against an Iran/Contra perjury indictment of former secretary of Defense (and editorial page contributor) Caspar Weinberger, this was its main evidence for Weinberger’s innocence: “Mr. Weinberger has taken and passed a lie-detector test on the matter.�


The Continuing Decline of McDonald’s : The Corbett Report (10-Jan-2017)

The global giant’s [McDonald’s] influential PR machine has used sleight-of-hand and other tricks to make this restructuring look like a smash success. They used their cheerleaders at the Wall Street Journal to hype “stronger-than-expected� profit and sales figures and their boosters at US News & World Report to hype some highly-selective earnings comparisons suggesting that this “turnaround� is, to use the WSJ’s phrase, “sustainable.�

But one doesn’t have to scratch too hard to reveal the rusty reality beneath this PR paint job.

Wall Street Journal circulation scam claims senior Murdoch executive | Media | The Guardian (12-Oct-2011)

One of Rupert Murdoch’s most senior European executives has resigned following Guardian inquiries about a circulation scam at News Corporation’s flagship newspaper, the Wall Street Journal.

The Guardian found evidence that the Journal had been channelling money through European companies in order to secretly buy thousands of copies of its own paper at a knock-down rate, misleading readers and advertisers about the Journal’s true circulation.

WSJ sourced Obama skinny quotes from Yahoo Message Boards (4-Aug-2008)

A journalist at the Wall Street Journal has been caught sourcing quotes for an article on Barak Obama being too thin to be President from a Yahoo Message Board.

In the article Too Fit to be President?, Wall Street Journal political correspondent Amy Chozick endeavored in the best News Corp tabloid style to create a story around the rather bizarre notion that voters wouldn’t vote for Obama because he was too thin, saying that “some Americans wondering whether he is truly like them.�

In the piece, she includes the quote “I won’t vote for any beanpole guy,� and originally didn’t attribute the source. Sadly No reports that the source was a Yahoo Message Board where Chozick actually asked for negative comments using her own name:

Plagiarizing? If the President Can Do it, Why Can’t We? – (article removed) (28-Dec-2009)

An online columnist for the Wall Street Journal was caught plagiarizing. Freelance writer Mona Sarika, who wrote the “New Global Indian� online column, used content from the Washington Post, Little India, India Today and San Francisco magazine.

Sarika copied direct quotes from other articles, without providing sources. She also changed the original speakers’ names apparently making up new ones.

WSJ Fakes a Green Shift Toward Nuclear Power | FAIR (24-Jun-2016)

The Wall Street Journal has a long history of editorial page support for nuclear power (4/17/01; 8/5/09; 11/9/09; 4/6/11; 5/24/13, to cite but a few) and against wind power (5/22/06, 3/1/10, 8/24/10, 11/8/12, 5/18/14 and others). In publishing this piece as edited, perhaps it is telling a story it wishes were true. As Harder’s article itself acknowledges, nuclear power is in decline due to a combination of economics, displacement by renewables and opposition. The green groups’ supposed change of heart “comes at a critical time, as several financially struggling reactors are set to shut down� even as other reactors already have, due to the low price of natural gas and state policies “that favor renewables over nuclear power.� As if to prove that point, the story provided a list of a dozen reactors that have been or will soon be shut down.

At Wall Street Journal, Government-Enforced Monopolies = ‘Free Market’ | FAIR (22-Jul-2015)

Ingram bizarrely touts the “flowing pipeline of new wonder drugs spurred by a free market,� which he warns will be stopped by “government price controls.� This juxtaposition is bizarre, because patent monopolies are 180 degrees at odds with the free market. These monopolies are a government policy to provide incentives for innovation. Ingram obviously likes this policy, but that doesn’t make it the “free market.�

Yes, Wall Street Journal, It’s Possible to Be Not Generous Enough | FAIR (10-Mar-2015)

The Wall Street Journal is soon to run a piece on improper denials of disability claims.

That’s inevitable, since any fair-minded newspaper that ran a column on improper approvals would surely want to balance it out.

At Wall Street Journal, Reporting Assault Through Israel’s Eyes | FAIR (13-Jul-2013)

In a news report on the Israeli military’s investigation of its own deadly raid on the Gaza aid flotilla, the Wall Street Journal (7/13/10) passes off as fact, with no qualifier, the Israeli government’s claim that members of IHH, a Turkish humanitarian organization, “attacked the Israeli soldiers as they boarded the ship.�

On Islamist Terrorism, WSJ Entitled to Its Own Opinions—But Not Its Own Facts | FAIR (16-Mar-2011)

This is a complete misrepresentation of the Rand report. The report is exclusively about Muslim radicalization and jihadism, not about domestic terrorism in general, as the WSJ would lead you to believe—if anything, it’s surprising that there are any non-Muslim jihadist plotters. (The exceptions were two men who agreed for their own secular purposes to collaborate with undercover FBI informants purporting to work for Al-Qaeda.)

The vast majority of “homegrown� terrorist attackers—those of all ideologies who successfully carry out an attack—are not Muslim, the report finds: Of the “83 terrorist attacks in the United States between 9/11 and the end of 2009, only three…were clearly connected with the jihadist cause.�

I could go on and on for months and months digging out the literal fake news pumped out by the Wall Street Journal or any other mainstream publication, but you can do that yourself if you’re so inclined. The point is, it is the mainstream media that is garbage; that is FAKE NEWS. Why? Simple: greed. Whenever there is greed involved — greed for money or greed for power or greed for control — there will always be corruption. Now granted, there is certainly boatloads of disinformation and misinformation all over the world wide web, but mixed in there are also some highly ethical people and small organizations that actually report the facts and back them with references. And who the hell is a multi-million dollar corporation (Mozilla) to dictate to you or i who is creditable and who is not? I have been watching probably an average of 50-100 news sites almost daily for many years and as a result of studying these sites and fact checking their content, i can confidently suggest some real news sites to follow if you’re interested:

How about NPR, Mozilla? Are they a creditable resource? I’ll bet they are in your eyes.

It is sites like those listed above that are actively being targeted by war-mongering, self-serving, psychopathic globalists who profit from endless war and stunting the development of the human species. The truth is irrelevant; all that matters is that you and i swallow whatever story it is that supports whatever agenda is being promoted at the moment by whatever government or corporation promoting it and now, to my surprise, even Mozilla has joined the ranks of those that want to control what information is available on the web, an architecture that was built with the free flow of information at its heart.

There must be some sort of funding that is being dished out to those willing to get on the “fake news” bandwagon. There is quite obviously a huge push to combat so-called “fake news” and return the masses to digesting the puke that spews out of the rancid bellies of corporate giants like the Wall Street Journal, the New York Times and all the rest of the mainstream presstitutes. Facebook, Google, Youtube – they are all doing the same thing. Are they getting paid to censor? Is Mozilla getting paid to take part in this? I don’t know, but i just may dig in and find out one of these days.

From The Mozilla Information Trust Initiative article:

This is why we’re launching MITI. We’re investing in people, programs, and projects that disrupt misinformation online.

Why Mozilla? The spread of misinformation violates nearly every tenet of the Mozilla Manifesto, our guiding doctrine.

Disrupt? So you want to use your corporate leverage to “disrupt” the flow of information? Sounds a lot like censorship, doesn’t it? Is that the principle on which the internet was built? From the Mozilla Manifesto:

The Internet is a global public resource that must remain open and accessible.

Well tell us Mozilla, how is it that the internet can remain open and equally accessible when corporate gate-keepers intend to steer the rest of us in a direction that benefits the powerful few and leads to total information control for the rest of us?

I think i’ll take their survey once again. In the mean time, go screw yourself Mozilla – i’ll do my own homework and decide what’s fake news and what isn’t.