-
Notifications
You must be signed in to change notification settings - Fork 42
Frequently Asked Questions
Issues are open, so click the issues tab below the repository name link on top of the page, and try to be as descriptive as you can be with the problem you found in any of the files of this repository. Any problem that is NOT directly related to any of the files here will be closed without further warning.
The theme here was created back when the default dark theme didn't cover any about: page, nor any menu/sidebar, and when no other full theme existed. Since then, Firefox default dark theme was updated to cover many of these elements (if still missing some dialogs), so there isn't much of a need for an external theme anymore. If you are using Windows or any other OS that paints all program dialogs white, you can install any custom theme to paint them dark (there are plenty in deviantart), which will also affect Firefox dialogs.
I made this theme for personal use since I didn't like how everything was flashing white, but now it's not really needed anymore, so I stopped working on upgrading it as often. This doesn't mean that I won't patch things in it (since I still use it myself), but I won't be trying to make installers for the theme part.
Right now the focus is on the Javascript functions that can't be emulated with webextensions.
Make sure you downloaded the raw files from the repository (either cloning the whole repository, downloading the RAW version of the files, or copying the code you are interested in to your userChrome.css), and place them inside the chrome folder inside the root profile folder (more information on that inside the dark theme section of this repository).
If you are using Firefox 69+, you also need to have enabled toolkit.legacyUserProfileCustomizations.stylesheets in about:config for userChrome or userContent (or any file in the chrome folder) to be loaded at all as per bug #1541233.
If you instead are only using the multi-row files, make sure that you patched firefox either automatically with the available patcher, or manually patching the root folder along with the chrome folder as explained in JS Loader.
The fastest way to solve the "blinking" white screen is to change the default web background color on Firefox settings > General > "Colors..." button > Background, which will make the blinking disappear and be changed to the color you set up. This, although, can cause some issues on some very few and specific pages like BBC, where they don't set a background color to override the one set here (the number of sites with this problem is very small, most sites override the background color set by this setting).
If not using userChrome from this theme, you will also have to add this to your userChrome.css file:
/* v Fix to make the pre-render loading page dark instead of white v */
#tabbrowser-tabpanels, #appcontent {background-color: #202025 !important}Since this only happens when not using a persona, either install a lightweight theme, or uncomment the rule in line 38 (#TabsToolbar one) on userChrome.css. To do so, just delete the ending "/*" in the line above it.
This only happens when using Firefox default theme, either use firefox built-in dark theme along with this one, or use any other lightweight theme you like.
If you only want the dark theme, use the default userChrome.css file inside Full dark theme, which won't make the context menu commands disappear unlike the one inside Dark theme + CSS tweaks userchrome. In case you want to use the features part of the theme, just delete everything after the line that says /* CONTEXT MENU COMMANDS */ (you can find it using the search option on notepad, or the code editor you are using).
In case you still want to delete some commands but not all, just comment out the ones that you want to appear, and leave as active the ones that you want to disappear.
For example, this is active, so the command is hidden:
/* Send image... */
#context-sendimage,...But this is commented out, so the command will show on the context menu:
/* Send image... *//*
#context-sendimage,*/You will see that the ones that I have commented out by default only have the starting /* of the comment after the description of what they are, since the closing */ would come from the next description comment below them.
The bookmarks toolbar text/tabs text color is black and I can't see the letters over the dark background.
This is caused by your persona (lightweight theme), and while you could change these settings inside userChrome, I thought it was better to just change the settings on the persona directly (since not all personas will look the same). To do so you'd have to open about:config, and search for lightweightThemes.usedThemes. Once there, find the textcolor setting and type any color you'd want to use instead of black or the color being used by the theme (use #fff for white). The persona you are currently using should be in the first place in the list.
If you only want to use multirow or any other javascript function, then you just need to use the patcher to install it automatically, or do the manual installation following the steps from the JS Loader folder. You don't need to use userChrome.css nor userContent.css for this at all with the new patching method.
I'm opening web files locally (as in opening html pages that you have created or downloaded) and the background is not the color it should be.
To change the directory browsing page and change how .css or some .txt files appear when opened with Firefox, I had to specify it to affect urls that start with file:///, meaning that any file opened with Firefox will get overriden with those rules as well. To prevent this, go to userContent.css, and comment out the lines that affect this url (This rule should be exactly under the color variables at the start of the file).
While we only needed to use CSS to enable multi-row tabs, this breaks tabs draggability, making reordering tabs when it was enabled a bit erratic, so to fix this, I decided to put all multi-row tabs code inside the MultiRowTabLiteforFx.uc.js file.
This means that now Multi-row tabs can be enabled installing it directly through the patcher. If you were using CSS code on your userChrome.css to enable multirow tabs, delete (or comment it out) for the js file to take effect instead.
The main reason is that you can't style firefox about: pages nor any part of it's interface with webextension addons (which are the only addons supported by Firefox right now) due to the webextensions API limitations, which is why we have to use these methods.
The theme is made so that it changes most background colors, including the one of the popups that don't have any background color specified by their original creator. Sadly it doesn't change the text of these by default, so you may have to do it manually, or report the addon you want themed here, or just use the fix inside userChrome.css (at the end of the file if you are using only the colors version) to turn the addons back to their white background color.