X
Tap here to go to the mobile version of the site.

Support Forum

List of ALL parameters and settings allowed in userchrome.css

Posted

Please provide a link to a reference for all of the parameters and options that are controllable by setting withing userchrome.css.

Thank you

Please provide a link to a reference for all of the parameters and options that are controllable by setting withing userchrome.css. Thank you

Additional System Details

Installed Plug-ins

  • Adobe PDF Plug-In For Firefox and Netscape 15.7.20033
  • Google Update
  • Office Authorization plug-in for NPAPI browsers
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • np-mswmp
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Shockwave Flash 18.0 r0
  • 5.1.40416.0

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0

More Information

snitch_ninja 1 solutions 14 answers

http://kb.mozillazine.org/Chrome_element_names_and_IDs

I can't really verify if that link includes ALL parameters...

does it

it should

EDIT
There is no comprehensive listing of every single possible selector to use when styling the user interface (just as it would be silly to create such a comprehensive list for a web page), but a few of the more common and interesting selectors are listed below.

it doesnt

sry

http://kb.mozillazine.org/Chrome_element_names_and_IDs I can't really verify if that link includes ALL parameters... does it it should :EDIT <blockquote> There is no comprehensive listing of every single possible selector to use when styling the user interface (just as it would be silly to create such a comprehensive list for a web page), but a few of the more common and interesting selectors are listed below. </blockquote> it doesnt sry

Modified by snitch_ninja

Question owner

I found that. It is far from complete. I know, for example, that items such as the following are valid...

menuitem[command="Browser:BookmarkAllTabs" toolbarbutton.bookmark-item > .toolbarbutton-icon bookmarksShowAll organizeBookmarksSeparator


I have found nothing at all the shows all such parameters/options. Thank you for your input though.

I found that. It is far from complete. I know, for example, that items such as the following are valid... menuitem[command="Browser:BookmarkAllTabs" toolbarbutton.bookmark-item > .toolbarbutton-icon bookmarksShowAll organizeBookmarksSeparator I have found nothing at all the shows all such parameters/options. Thank you for your input though.

Question owner

It would not at all be silly to do so, and in fact there are multiple on line references for the legal parameters for most web page languages (HTML, PHP, Ruby, etc). It is actually quite absurd that such a list does not exist.

It would not at all be silly to do so, and in fact there are multiple on line references for the legal parameters for most web page languages (HTML, PHP, Ruby, etc). It is actually quite absurd that such a list does not exist.
cor-el
  • Top 10 Contributor
  • Moderator
17536 solutions 158573 answers

Your imagination is the limit. It is not possible to have a complete list. Use the DOM Inspector or check the source code if you need information about specific elements.


Your imagination is the limit. It is not possible to have a complete list. Use the DOM Inspector or check the source code if you need information about specific elements. *DOM Inspector: https://addons.mozilla.org/firefox/addon/dom-inspector-6622/ *https://developer.mozilla.org/DOM_Inspector *https://developer.mozilla.org/Introduction_to_DOM_Inspector ---- *https://developer.mozilla.org/Web/Guide/CSS/Getting_started/Selectors

Question owner

Seriously? READ THE SOURCE CODE? Surely you are not a programmer with an answer like that. That has the be the most laughable answer to any question ever asked on the internet. Thanks anyway.

Seriously? READ THE SOURCE CODE? Surely you are not a programmer with an answer like that. That has the be the most laughable answer to any question ever asked on the internet. Thanks anyway.

Question owner

Quite actually it is possible to have a list. In fact it is absurd to NOT have one. It is lazy to not have one. There should be a master list of all customization parameters for FireFox. For example, the parameters to hide/display the history or bookmarks items in the main menu should be documented somewhere. They HAVE TO be or else no one would know them. They HAVE TO be documented somewhere or FF would not even work.

Quite actually it is possible to have a list. In fact it is absurd to NOT have one. It is lazy to not have one. There should be a master list of all customization parameters for FireFox. For example, the parameters to hide/display the history or bookmarks items in the main menu should be documented somewhere. They HAVE TO be or else no one would know them. They HAVE TO be documented somewhere or FF would not even work.
cor-el
  • Top 10 Contributor
  • Moderator
17536 solutions 158573 answers

Did you read the article about selectors?

You will have to make yourself familiar with the DOM Inspector to find the selectors and to compose your own CSS rules.

Did you read the article about selectors? *https://developer.mozilla.org/Web/Guide/CSS/Getting_started/Selectors You will have to make yourself familiar with the DOM Inspector to find the selectors and to compose your own CSS rules.

Question owner

I am fully aware of how css is written. I do not need a primer on css, I need a list of valid parameters for FF is all.

Thank you for your continued input.

I am fully aware of how css is written. I do not need a primer on css, I need a list of valid parameters for FF is all. Thank you for your continued input.
cor-el
  • Top 10 Contributor
  • Moderator
17536 solutions 158573 answers

A browser like Firefox has tens of thousands of elements and each of them can have its own attributes that can be used as additional selectors like you posted above (menuitem[command="..."]). It is impossible to create a comprehensive list and include version information to what Fx versions it applies. If an element has an ID then you use that ID and otherwise revert to a class name or a unique selector that starts with an ID.

A file like browser.css already has a lot of style rules.

  • chrome://browser/content/browser.css
  • chrome://browser/skin/browser.css

  • resource:///chrome/browser/skin/classic/
  • resource://gre/chrome/toolkit/skin/classic/
A browser like Firefox has tens of thousands of elements and each of them can have its own attributes that can be used as additional selectors like you posted above (menuitem[command="..."]). It is impossible to create a comprehensive list and include version information to what Fx versions it applies. If an element has an ID then you use that ID and otherwise revert to a class name or a unique selector that starts with an ID. A file like browser.css already has a lot of style rules. *chrome://browser/content/browser.css *chrome://browser/skin/browser.css ---- *resource:///chrome/browser/skin/classic/ *resource://gre/chrome/toolkit/skin/classic/

Modified by cor-el

the-edmeister
  • Top 25 Contributor
  • Moderator
5406 solutions 40241 answers

FrogSteaks said

Quite actually it is possible to have a list. In fact it is absurd to NOT have one. It is lazy to not have one. There should be a master list of all customization parameters for FireFox. For example, the parameters to hide/display the history or bookmarks items in the main menu should be documented somewhere. They HAVE TO be or else no one would know them. They HAVE TO be documented somewhere or FF would not even work.

You can volunteer your services to create such a list.

''FrogSteaks [[#answer-751497|said]]'' <blockquote> Quite actually it is possible to have a list. In fact it is absurd to NOT have one. It is lazy to not have one. There should be a master list of all customization parameters for FireFox. For example, the parameters to hide/display the history or bookmarks items in the main menu should be documented somewhere. They HAVE TO be or else no one would know them. They HAVE TO be documented somewhere or FF would not even work. </blockquote> You can volunteer your services to create such a list.

Question owner

Cor the DOM does nothing to help me with what I am looking for (as fr as I can see). It inspects the web page currently loaded. I want to be able to control the layout and look/feel of FF itself. Is there a way to have DOM inspect the FF UI itself?

Cor the DOM does nothing to help me with what I am looking for (as fr as I can see). It inspects the web page currently loaded. I want to be able to control the layout and look/feel of FF itself. Is there a way to have DOM inspect the FF UI itself?

Question owner

the-edmeister said

FrogSteaks said
Quite actually it is possible to have a list. In fact it is absurd to NOT have one. It is lazy to not have one. There should be a master list of all customization parameters for FireFox. For example, the parameters to hide/display the history or bookmarks items in the main menu should be documented somewhere. They HAVE TO be or else no one would know them. They HAVE TO be documented somewhere or FF would not even work.

You can volunteer your services to create such a list.

Well gee Wally that was so very helpful. Perhaps if I knew the available parameters I would not be asking where I can find them.

''the-edmeister [[#answer-751520|said]]'' <blockquote> ''FrogSteaks [[#answer-751497|said]]'' <blockquote> Quite actually it is possible to have a list. In fact it is absurd to NOT have one. It is lazy to not have one. There should be a master list of all customization parameters for FireFox. For example, the parameters to hide/display the history or bookmarks items in the main menu should be documented somewhere. They HAVE TO be or else no one would know them. They HAVE TO be documented somewhere or FF would not even work. </blockquote> You can volunteer your services to create such a list. </blockquote> Well gee Wally that was so very helpful. Perhaps if I knew the available parameters I would not be asking where I can find them.
cor-el
  • Top 10 Contributor
  • Moderator
17536 solutions 158573 answers

The DOM Inspector (DOMi) has a menu item (Edit > Select Element By Click) and a toolbar button "Find a node to inspect by clicking on it" (left icon on the toolbar in the DOMi).

  • open the browser window in the DOMi (File > Inspect Chrome Document) and choose the first entry from the drop-down list.
  • click the "Find a node to inspect by clicking on it" button and use the keyboard (Alt Tab) or the Task bar to go back to the browser window (do not click in the browser window other than the title bar).
  • click that element with the mouse and keep the button pressed until you see a red border to indicate that the DOMi has located that element in the DOM tree.

See also:

The DOM Inspector (DOMi) has a menu item (Edit > Select Element By Click) and a toolbar button "Find a node to inspect by clicking on it" (left icon on the toolbar in the DOMi). * open the browser window in the DOMi (File > Inspect <b>Chrome</b> Document) and choose the first entry from the drop-down list. * click the "Find a node to inspect by clicking on it" button and use the keyboard (Alt Tab) or the Task bar to go back to the browser window (do not click in the browser window other than the title bar). * click that element with the mouse and keep the button pressed until you see a red border to indicate that the DOMi has located that element in the DOM tree. See also: *https://developer.mozilla.org/Introduction_to_DOM_Inspector