Firebug had an option to filter CSS rules to only display the applied styles. This feature should be added to the Rules view. That could be done by adding a new button besides the filter field to toggle their display or by adding some way to filter them out via the filter field, e.g. via a special filter tag. FWIW, this was asked for in http://superuser.com/q/1173414/324429. Sebastian
Perhaps a new operator inside the filter field? Something like status:applied It could work in combination with other filters: `color` status:applied would display all the `color` properties that are applied. color status:applied would display all properties containing color that are applied. status:applied would display all properties that are applied. Perhaps we could have extra values for status as well: overriden/unapplied/...
Also, we could have a preference that allows setting a default value for the filter input or maybe persisting the filter input value.
Thanks Tim! That's what I had in mind when I wrote "filter tag". The entered filter value is already persisted as long as the DevTools are open for a tab. So, that's ok, IMO. If the option should be persisted even across browser sessions, I think a button or checkbox might be a better UI than a pre-filled input field. There's also another thing to consider with persisting the filter: People may want to keep the applied styles option activated while filter keywords like 'color' probably change more often. After all, If operators are added, they should be autocompleted. Otherwise users won't get to know about them. And having to type them everytime is tedious. Sebastian
Inspector bug triage (filter on CLIMBING SHOES).
Severity: normal → enhancement
Priority: -- → P2
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.