Closed Bug 201829 Opened 22 years ago Closed 6 years ago

Highlight non-inherited styles in "Computed Style" panel

Categories

(Other Applications :: DOM Inspector, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jruderman, Unassigned)

Details

It would be easier to pick out the relevant styles in the "Computed Styles" panel if non-inhertied styles were in bold. (cf about:config, which shows non-default prefs in bold.) I'm not sure which method would be better/easier for determining which properties to show in bold: * Properties that are not inherited. (Background would be "transparent" and bold for most elements.) * Properties that do not match parent's properties. (Some properties would not be bold even though a selector matched, just because the parent happened to have the same value for that property. Also, a default value of "transparent" would sometimes be bold.)
The latter would be doable in almost all instances, I think; we'd have to compare the computed style of the node versus the computed style of its parent node (if not null). jruderman: For the document.documentElement node, what do you suggest? There is no parent element to compare against...
For document.documentElement, I think it would make more sense to show everything in bold than to show nothing in bold.
How about looking through all the matching rules and bolding any properties that are mentioned?
OS: Windows XP → All
Hardware: PC → All
Hm... Yeah, that should be fairly easy to do (even using just the CSSOM APIs).
Mass re-assigning bugs to dom.inspector@extensions.bugs
Assignee: caillon → dom.inspector
Product: Core → Other Applications
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
Bulk close. This component is no longer supported or maintained. https://bugzilla.mozilla.org/show_bug.cgi?id=1499023
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Bulk close. This component is no longer supported or maintained. https://bugzilla.mozilla.org/show_bug.cgi?id=1499023
You need to log in before you can comment on or make changes to this bug.