Closed Bug 770357 Opened 13 years ago Closed 11 years ago

[rule view] show invalid css properties and values

Categories

(DevTools :: Inspector, defect, P3)

15 Branch
x86
macOS
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 984880

People

(Reporter: groovecoder, Unassigned)

References

Details

Steps to reproduce: 1. Add table.diff { font: "Courier New", "Andale Mono", monospace; } to your CSS. 2. Inspect table.diff element Expected results: Show font property and value along with a warning about improper value (e.g., Chrome inspector) Actual results: font property isn't shown at all making me believe my CSS isn't refreshing.
I agree, this is confusing. As for bug 752881, we need to show the properties as originally written. We use domUtils.getCSSStyleRules to retrieve the rules. And it only return valid declarations. Afaik, there are no ways to get the rules as authored. I think we'll need some platform work here.
Bug triage, filter on PINKISBEAUTIFUL
Priority: -- → P3
Summary: show invalid css properties and values → [rule view] show invalid css properties and values
I think we should consider bumping this up to P2.
Blocks: 913661
I've also opened Bug 913661 to deal with showing multiple declarations of the same name (not just the last one). I think this also depends on the ability to get rules as authored.
Depends on: 752881
This would be a massive improvement for mobile web compat work - we're dealing a lot with layout issues caused by -webkit- properties, and currently the most "efficient" way to analyse those issues is to run both Chrome and Firefox inspectors side by side for a manual comparison of the styling applied to a given element. Having all those -webkit- rules right there, styled in red or something, would be extremely helpful to us.
(There's also bug 740538 - closely related)
Duplicate of bug 984880 which already has a patch uploaded. It's only a work in progress for now though.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.