New issue
Advanced search Search tips

Issue 698519 link

Starred by 2 users
Status: Archived
Owner:
einbinder@chromium.org
Closed: Oct 31
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

nonsense style information

Reported by teo8...@gmail.com, Mar 4 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
See the screenshot

What is the expected behavior?
The element's display property has either a computed value of "block" or "inline-block" (or any of the other possible values). 
Either way, the compute value must coincide with the value from the topmost non-striked-through rule displayed just below

What went wrong?
The devtools are telling me that the computed value is "block", and that the prevailing rule dictates a value of "inline-block". One thing contraddicts the other, this is pure NONSENSE.

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 24.0 r0

I'm fucking SICK of this kind of bugs

Comment 1 by teo8...@gmail.com, Mar 4 2017 

I see, this is because there's another rule that sets float: left.

This reproduces the issue: http://output.jsbin.com/gunazovibu

I guess a value other than "none" for float implies that the computed value of display is forced to "block".

The issue is that the information given here by the style panel is pathetically insufficient. By expanding the triangle next to the computed value I expect it to tell me EVERYTHING about why the computed value is what it is. If you tell me that the computed value is X and that the only (or prevailing) applied rule dictates a value of Y, you MUST tell me why the value is X and not Y.

So:
- the rule that says "inline-block" should have a strike-through line
- some clue should be given about the related property (in this case "float") that is forcing another value

Comment 2 by paulir...@chromium.org, Mar 6 2017 

Yeah it's kind of crazy. I've run into this myself as well.

But check out the spec: https://drafts.csswg.org/css-display/#transformations
(attached)

Basically float makes `display` just immediately go to block. 
But that's how the CSS specs have defined things... so yeah.

I mean Ideally it'd be great if Computed Style said "it's block because its floated", but i don't think we can pull that off right now. :/
Screen Shot 2017-03-06 at 2.18.58 PM.png
147 KB View Download

Comment 3 by kavvaru@chromium.org, Mar 7 2017

Labels: TE-NeedsTriageHelp

Comment 4 by einbinder@chromium.org, Mar 21 2017

Owner: einbinder@chromium.org
Status: Assigned (was: Unconfirmed)
This seems fixable. We can add some new logic to CSSMetadata

Comment 5 by dgozman@chromium.org, Oct 31

Status: Archived (was: Assigned)
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix.
►

Sign in to add a comment