See:

• https://developer.mozilla.org/en/Tools/Page_Inspector
• https://developer.mozilla.org/en/Tools/Page_Inspector/Style_panel
• https://developer.mozilla.org/en/Tools/Style_Editor

Thank you for your response. Those links explain the basic functions of the tool pretty well, but unfortunately don't answer my question. Either I've misunderstood something I read, or maybe what I want isn't actually possible.

Let me be more specific: I have an entire website on my local machine that I did DLed but did not create. Looking at style elements on the live site, I'd like to know the exact filepath to a given style.

Thank you

If you have opened the inspector and have selected an element then the Rules tab shows all rules that are found and in which file and line. A click on that link opens the style editor window that allows live editing of CSS rules and save the changes.

You can also look at the DOM Inspector.

• https://developer.mozilla.org/En/DOM_Inspector
• https://developer.mozilla.org/en/Introduction_to_DOM_Inspector

• DOM Inspector: https://addons.mozilla.org/firefox/addon/dom-inspector-6622/

cor-el, I really appreciate you taking the time to help, and I realize I may seem slow, but when I highlight an element whose filepath I want, I'm getting this:

element { inline

   font-size: 88%;
   z-index: 0;
   position: static;
   display: block;
   background-color: rgb(153, 204, 255);

}

...which is great, but where is this block located? I can click on "inline", which opens up a page of html code, but the above is not present on the opened page.

I know I'm missing something here. So close...

If the CSS code is inline then it should be in the main HTML file, but it is possible that the position (line number) is not known, so you may need to do a search via Ctrl+F.

• https://developer.mozilla.org/en/Tools/Using_the_Source_Editor

Styles that are otherwise added via an extension like stylish or userContent.css will probably also show as inline CSS code.

I would have to look at such a page to see what is happening in your case.

Did you try the DOM Inspector?