Maybe my workflow is just wrong, but I came across this UX several times already and am not happy about it. STR / Here's my workflow: 1. Have some kind of weird layout and no idea where this comes from 2. Rule view does not help: I just cannot find the rule that is causing this 3. So I go to "Computed" CSS view to see just all properties and scan through them 4. I find some property being calculated which does not look correct to me AR: - I cannot edit the value there (which I want to test if my suspicion is correct) - Clicking on the file link brings my to the "Style Editor" (completely new context as I have been in the Rule View before) ER: - Let me edit values in the Computed CSS Rule - Clicking a link next to the computed rule brings me back to the ruleview jumping directly to the matching CSS rule. After all, this is how it all started: I was looking for a certain rule. In the rule view I can edit. TBH, I do not use the Style Editor at all normally. I guess most people edit CSS in their preferred editor/IDE and then just use the devtools' rule view.
Hi Jens, Thanks for filing this. I agree we need to provide a better UX in the Computed view when working with the rest of the other views in the Inspector. Will be looking into this in the near future. Thanks, Gabriel
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.