New issue
Advanced search Search tips

Issue 900938 link

Starred by 1 user
Status: Assigned
Owner:
l...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: offer help/indication when computed style has contradictions

Reported by teo8...@gmail.com, Nov 1 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Steps to reproduce the problem:
See https://bugs.chromium.org/p/chromium/issues/detail?id=698519

What is the expected behavior?

What went wrong?
The issue got closed because of "Bulk closing low-priority issues with no activity"

I don't know who labled that as "low priority" (it should be pretty high priority as it basically defeats the whole purpose of the style panel in DevTools), and especially I don't see why "with no activity" should be a criterion for closing issues at all.

The comment says:
"Please re-file and refer to the closed issue if it's essential to fix"

so this is what I'm doing, because it's essential to fix (though I don't see why we should open a new issue rather than reopen the original one; I guess it's a way to improve your statistics on issues, I can't see any other reason)

Did this work before? No 

Chrome version: 69.0.3497.100  Channel: n/a
OS Version: 
Flash Version:

Comment 1 by l...@chromium.org, Nov 2

Owner: l...@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: DevTools: offer help/indication when computed style has contradictions (was: contraddictory/insufficient style information)
Thanks for the report.  The Computed Styles pane always shows the computed value, interpreted by the browser, even if that differs from what the stylesheet provides.

Based on the linked crbug's c#1,

> the rule that says "inline-block" should have a strike-through line
Showing strikethrough when there is a mismatch sounds reasonable to me.

> some clue should be given about the related property (in this case "float") that is forcing another value
Adding an explanation that is intuitive, concise, and specific is a challenge to implement and maintain.  Chromium often doesn't provide DevTools "reasons why" a value is chosen, so the most naive approach is to say: "the browser's CSS engine has transformed the given property's value".

Ideally, we could also link to an external website that explains all the possible ways this could happen.  I don't know if one exists, however.

I'll take a look at the work for UX without introducing explanations.

Related: https://github.com/w3c/csswg-drafts/issues/1355
►

Sign in to add a comment