Bug 130120 - Web Inspector: Computed style incorrect for tables set to display: table-row-group
Summary: Web Inspector: Computed style incorrect for tables set to display: table-row-...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
Keywords: InRadar
Depends on:
Blocks: 129369
  Show dependency treegraph
Reported: 2014-03-12 00:16 PDT by James Craig
Modified: 2016-12-13 15:35 PST (History)
3 users (show)

See Also:

test case (last table in the page) (13.82 KB, text/html)
2014-03-12 00:16 PDT, James Craig
no flags Details
screen shot (173.14 KB, image/png)
2014-03-12 00:18 PDT, James Craig
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Craig 2014-03-12 00:16:53 PDT
Created attachment 226481 [details]
test case (last table in the page)

Web Inspector: Computed style incorrect for tables set to display: table-row-group

We're trying to track down a data table heuristics bug in bug 129369, and although the styles for the last table in the test case are set to display: table-row-group, the computed styles still come out as display: table. There might be a CSS bug here too, but at the very least there is a Web Inspector bug in that the style rules inspector shows the table-row-group styles applied (no strikethrough) yet the computed styles panel shows something else. Screen shot also shows that JS and CSSOM indicate the display property is the expected value, not what the Web Inspector displays in computed styles.
Comment 1 James Craig 2014-03-12 00:18:05 PDT
Created attachment 226482 [details]
screen shot
Comment 2 Timothy Hatcher 2014-03-12 12:03:35 PDT
I think the Inspector is showing the right thing. WebCore is likely taking the table-row-group values and converting it to table since it is not in a table parent?

Computed style is likely correct (what WebCore is doing) and the $0.style object just parrots back the data.

But there is likely an Inspector UI bug where this is using table-row-group and not getting what we expect.
Comment 3 James Craig 2014-03-12 23:40:33 PDT
More info: Results differ based on where this uses quirks mode rendering. Add a doctype and you get the expected values. 

Based on that, I think you're right that computed style is showing the right thing, but the Inspector UI bug is that the Rules tab of the Styles Inspector does now indicate that the rules are being overridden by the quirksmode rendering.
Comment 4 James Craig 2014-03-12 23:41:07 PDT
Comment 5 David Kilzer (:ddkilzer) 2016-09-09 11:12:08 PDT