New changelog created

To stay up-to-date with all changes made to this repository, please see here.

Important Update 11/29/2017

Some extensions have preferences built into the about:addon page that do not utilize the default styling settings utilized by Firefox.

Due to this, some compatibility issues may arise (such as Tree Style Tabs), or simply undesirable/ugly appearances (such as Stylus).

Current workaround:

Additional code is being written to resolve this. Since not all users use the same extensions, the code will not be placed in the main userContent.css file. Instead, they will be placed in individual files - one file per extension - in the webextension-tweaks folder. To use these files, do the following:

• Download the corresponding css file of interest, and put it in a folder titled webextension-tweaks within your chrome directory

• Go to about:debugging#addons and find the corresponding addon.

• Copy the Internal UUID of the extension

• Replace the ID in the css file you downloaded with this ID

• In your userContent.css file, add an import statement at the top of the file. For example, @import "webextension-tweaks/tree_style_tabs.css";

• Save all your files and restart your browser.

userContent-tweaks

Currently, the scope of this project involves improving about pages for Firefox 57+ users who prefer a dark theme. Depending on available time and user contributions, this repository could evolve into a centralized location for all userContent.css tweaks.

Important Update 11/29/2017: Some extensions have preferences built into the about:addon page that do not utilize the default styling setting utilized by Firefox.

Due to this, some compatibility issues may arise (such as Tree Style Tabs), or simply undesirable/ugly appearances (such as Stylus).

What is userContent.css?

In short, userContent.css is a file used to define and customize web page content. This file does not exist in a Firefox profile by default, and must be created by the user.

Why userContent.css?

Firefox has restrictions on the pages extensions can access. Therefore, something such as Stylus can not be used to stlye about pages.

Where does the userContent.css file go?

Like userChrome.css, userContent.css resides in a subdirectoy titled chrome within your Firefox profile.

How do I get to my profile directory?

The location of your profile depends on your operating system. Nevertheless, the following steps should always work:

• Use the address bar to visit about:support

• Click on the Show in Finder/Show Folder button available next to the label Profile Finder.

I'm in my profile directory, what now?

Look for a folder titled chrome. This folder does not exist by default, so if you don't see it, create it yourself.

You can now download the zip file of this repository, and put the userContent.css file in your chrome folder.

*IMPORTANT: if you already have a userContent.css file, combine the contents of the two files as to not lose any changes you have made.

What do the changes look like?

Here are just a few examples:

Can I contribute?

Of course! Ideally, I would like this repository to be driven by user contributions. There are a large number of about pages, and I have just scratched the surface (to see them all, visit about:about). I would love to have your help completeing the rest. This project is truly in it's infancy, so please feel free to make suggestions, tell me where I've made mistakes, and let me know how you would like this repository to be shaped.

I'm open to anything, so if you would like to contribute in any way, please let me know. I don't want to limit this repository to only changes in about pages...that's just what I began working on. You can submit pull requests, or message me on Reddit if you have something you want to discuss/share :)

Edit: Due to some very helpful tips and suggestions, I was able to complete the rest of the about:pages (I think?)...so I no longer need help with that...yay!

I would still love your help finding areas to improve, things I messed, ways to improve the code etc.~

[ToDo]

Condense code where possible

Create variable so users can easily change the theme