userChrome
There is no userChrome.css in my profile.
If it needs to be created, where do I create it?
Yes, I searched for help. What I found was about userChrome.css to solve specific problems, but not what to do if it doesn't exist. Is userChrome still supported?
Thank you! Mark.
Wybrane rozwiązanie
AHA!!
What I need was not 'userChrome.css', but 'userContent.css'.
I put my custom style rules...
a:link{cursor:pointer !important;outline:green solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important}
a:visited{cursor:pointer !important;outline:red solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important}
...in 'userContent.css' and now the links in web pages are plainly shown as boxes. I'm happy. ...no more 'mousing' around to find links.
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (13)
WARNING from the moderator team: userChrome.css scripts are not provided by Mozilla and are not officially supported. Firefox is a work in progress and, to allow for continuous innovation, Mozilla cannot guarantee future updates won’t impact your customizations. For this reason, Mozilla does not officially support style rules customization.
Please read Firefox Advanced Customization and Configuration Options to learn more.
Paul said
WARNING from the moderator team: userChrome.css scripts are not provided by Mozilla and are not officially supported. Firefox is a work in progress and, to allow for continuous innovation, Mozilla cannot guarantee future updates won’t impact your customizations. For this reason, Mozilla does not officially support style rules customization. Please read Firefox Advanced Customization and Configuration Options to learn more.
I can't see web page links. It seems that either links are no longer underlined, or websmiths are suppressing them on the pages they write. For years I had a userChrome that boxed links so that I could see them. I had to recently install a new Linux Mint and FFox because there was no update path.
Yes, I take my own responsiblity.
Hi Mark, it always needs to be created. Did you find my site here: https://www.userchrome.org/
The userChrome made no difference. Why not?
Here are my userChrome: [code] mark@mark-VirtualBox:/media/sf_LinuxFFox/ckls0yge.default-release/chrome$ ls -l total 1 -rwxrwx--- 1 root vboxsf 272 Jul 5 17:10 userChrome.css mark@mark-VirtualBox:/media/sf_LinuxFFox/ckls0yge.default-release/chrome$ cat userChrome.css
- link{cursor:pointer !important;outline:green solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important}
- visited{cursor:pointer !important;outline:red solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important}
The userChrome above made no difference. Nothing happened to the sites with links.
Zmodyfikowany przez Mark Filipak w dniu
jscher2000 - Support Volunteer said
Hi Mark, it always needs to be created. Did you find my site here: https://www.userchrome.org/
Hi Jefferson,
So kind of you to contibute. My userChrome used to work. No longer. Look at my mate-terminal session. Got any ideas?
My heart goes out to you when you put time into creating a helpful site and it doesn't show up in searches and it isn't advertised in FFox. It's a shame.
Is there something I have to do to FFox to get it to honor userChrome.css?
PS: I just noticed that the terminal's cat listing didn't make it in intact. Here's the contents of userChrome.css
a:link{cursor:pointer !important;outline:green solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important} a:visited{cursor:pointer !important;outline:red solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important}
Zmodyfikowany przez Mark Filipak w dniu
jscher2000 - Support Volunteer said
Hi Mark, it always needs to be created. Did you find my site here: https://www.userchrome.org/
Regarding https://www.userchrome.org/: "At startup, Firefox checks for JavaScript files in the"
"program folder" ...program folder? '/bin/' or do you mean '~/.mozilla/firefox'?
"under /defaults/pref." ...do you mean '~/.mozilla/firefox/defaults/pref'? or do you mean '~/.mozilla/firefox/defaults/pref/'?
"An Autoconfig file — which may be named config-prefs.js, local-settings.js, or whatever.js — directs Firefox to load a JavaScript file (placed at the"
"top level" ...top level?
"of the program folder" ...program folder? "top level of the program folder"? Not at '~/.mozilla/firefox/defaults/pref' or '~/.mozilla/firefox/defaults/pref/'? I'm confused.
") that contains the actual script code."
"That second file" ...there's 2 files? Tip: When there are two major subjects, putting them in separate paragraphs will enhance understanding.
Zmodyfikowany przez Mark Filipak w dniu
jscher2000 - Support Volunteer said
Hi Mark, it always needs to be created. Did you find my site here: https://www.userchrome.org/
Regarding https://www.userchrome.org/: "At startup, Firefox checks for JavaScript files in the"
"program folder" ...program folder? '/bin/' or do you mean '~/.mozilla/firefox/'?
"under /defaults/pref." ...do you mean '~/.mozilla/firefox/defaults/pref'? or do you mean '~/.mozilla/firefox/defaults/pref/'?
"An Autoconfig file — which may be named config-prefs.js, local-settings.js, or whatever.js — directs Firefox to load a JavaScript file (placed at the"
"top level" ...top level?
"of the program folder" ...program folder? "top level of the program folder"? Not at '~/.mozilla/firefox/defaults/pref' or '~/.mozilla/firefox/defaults/pref/'? I'm confused.
") that contains the actual script code."
"That second file" ...there's 2 files? Tip: When there are two major subjects, putting them in separate paragraphs will enhance understanding.
You can use the autoconfig.cfg file in the Firefox installation folder to initialize (set/lock) preferences and run privileged JavaScript code. Since this file is in the Firefox installation folder, code in this file is applied to all profiles although you can restrict it via special JavaScript code. This is different from the userChrome.css (user interface) and userContent.css (websites and built-in about pages) files that are placed in the profile folder and thus only are active if Firefox uses this profile.
To use Autoconfig, place two files into the Firefox installation directory.
- on Windows, they go into the same directory where Firefox is installed
- on macOS, they go into the Contents/Resources directory of the Firefox.app
The autoconfig.js file that specifies to use autoconfig.cfg is placed into the "defaults\pref" directory where the channel-prefs.js file is located. The autoconfig.cfg file is placed at the top level of the Firefox directory.
- autoconfig.cfg and autoconfig.js need to start with a comment line (//)
- autoconfig.js needs to use Unix line endings (LF instead of CR/LF)
See also:
Zmodyfikowany przez cor-el w dniu
Wybrane rozwiązanie
AHA!!
What I need was not 'userChrome.css', but 'userContent.css'.
I put my custom style rules...
a:link{cursor:pointer !important;outline:green solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important}
a:visited{cursor:pointer !important;outline:red solid 0.1em !important;font-weight:bold !important;text-decoration:underline !important}
...in 'userContent.css' and now the links in web pages are plainly shown as boxes. I'm happy. ...no more 'mousing' around to find links.
cor-el said
You can use the autoconfig.cfg file in the Firefox installation folder ...
There is no such thing as "Firefox installation folder" in Linux. The closest thing to that would be '/bin/' but '/bin/firefox', though it is marked as a program, is only 168 bytes.
You should see the Application Binary folder listed on the "Help -> More Troubleshooting Information" (about:support) page.
cor-el said
See also:
Thank you for that. Honest, I tried to read it, but...
Where real documentarians begin with noteworthy examples, then go on to explanations & details, Linux developers give abstracted 'usage cases' using abstract labels with no examples. Codesmiths should not write documentation. They should comment their code (which they usually don't do) using a readable pseudo-code.