pmOS-tweaks/mobile-config-firefox
1
0
Fork 0
forked from fliegerjohn/mobile-config-firefox
Code Pull requests Activity

README: Move setup to the top right after intro (#93)

Browse source 
* README: Move setup to the top right after intro

Updated it from my own setup experience, added concrete steps

Also added the fact that restart may be needed (don't expect to see changes after just creating and saving the file)

Sorry Windows users :D  maybe someone can add Windows-specific things to the steps.

* Update README.md

typo fix
This commit is contained in:
Sigmundur 2021-03-07 08:36:49 +02:00 committed by GitHub
parent 78a5c1c287
commit 7a0c36eb35
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 25 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
README.md
View file

@ -6,21 +6,21 @@ In the case that a particular style relies on another style, the fact will be no
Stylesheets in this repository are tested only on Windows 10 and to a lesser amount on Linux. Most of them should also work on OSX and Windows7, but there may be wrong behavior especially when native widgets such as window titlebar or window control buttons are being styled. Stylesheets in this repository are tested only on Windows 10 and to a lesser amount on Linux. Most of them should also work on OSX and Windows7, but there may be wrong behavior especially when native widgets such as window titlebar or window control buttons are being styled.
# Style categories # Setup
The files themselves are only separated to *chrome* and *content* sub-folders. Files have a one or more *tag* applied to them as listed in `tags.csv` file.
You can browse the tag-categorized files by [using this simple ui](https://mrotherguy.github.io/firefox-csshacks/)
# Loading user*.css files
0. Go to about:config and set the pref `toolkit.legacyUserProfileCustomizations.stylesheets` to `true` to make Firefox load userChrome.css and userContent.css 0. Go to about:config and set the pref `toolkit.legacyUserProfileCustomizations.stylesheets` to `true` to make Firefox load userChrome.css and userContent.css
0. Find your profile folder and
* If Firefox is running you can find by going to `about:support` and there should be a button with label "Open Folder" under application basics
* On command-line, you can also find your firefox executable and run `firefox -ProfileManager`
0. Clone this repository in the profile folder
* `git clone https://github.com/MrOtherGuy/firefox-csshacks.git` on command-line (first `cd` into the profile directory of course!)
0. Rename the newly cloned repo to `chrome`
* `mv firefox-csshacks chrome`
0. `userChrome.css` and `userContent.css` files should be created inside this chrome-folder.
* You can copy-paste and modify lines from `userChrome_example.css` and `userContent_example.css` to get started
0. If Firefox is running, restart Firefox so that the changes take effect
1. Find your profile folder, if Firefox is running you can find by going to `about:support` and there should be a button with label "Open Folder" under application basics As an alternative to cloning this repository you can set up the `chrome` folder manually.
2. Create a new folder to the profile folder and name it "chrome"
3. `userChrome.css` and `userContent.css` files should be created inside this chrome-folder.
Clone this repository or individual files inside that newly created chrome-folder.
In the end you should have a folder structure like this: In the end you should have a folder structure like this:
``` ```
@ -39,6 +39,12 @@ all other profile folders and files
In short, create a parent chrome folder to the same directory where `prefs.js` is - the main profile folder. Firefox loads `userContent.css` and `userChrome.css` files only from that `chrome`-folder. In short, create a parent chrome folder to the same directory where `prefs.js` is - the main profile folder. Firefox loads `userContent.css` and `userChrome.css` files only from that `chrome`-folder.
# Style categories
The files themselves are only separated to *chrome* and *content* sub-folders. Files have a one or more *tag* applied to them as listed in `tags.csv` file.
You can browse the tag-categorized files by [using this simple ui](https://mrotherguy.github.io/firefox-csshacks/)
# Usage # Usage
Stylesheets are divided in to chrome and content folders. The difference is that styles inside "content" affect web-pages whereas styles inside "chrome" affect browser UI. Stylesheets are divided in to chrome and content folders. The difference is that styles inside "content" affect web-pages whereas styles inside "chrome" affect browser UI.