New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 736093 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Wrong computed 'writing-mode' style for table-row-group, table-row and table-cell

Project Member Reported by wangxianzhu@chromium.org, Jun 22 2017

Issue description

Chrome Version: ToT

What steps will reproduce the problem?
http://jsbin.com/suhejuk

What is the expected result?
The computed 'writing-mode' style of table-row-group, table-row and table-cell should be the specified value if specified or the inherited value.

What happens instead?
The computed 'writing-mode' style is always the same as the table.

I know that 'writing-mode' doesn't apply to table-row-group and table-row, but we should still respect the specified value and allow the specified value to be inherited.

Other browsers:
Safari: not tested. I guess it's the same as Chrome
Firefox: as expected
Edge: as expected.
 

Comment 1 by nainar@chromium.org, Jun 22 2017

Labels: Update-Quarterly
Status: Available (was: Untriaged)
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Available)
Cc: dgro...@chromium.org robhogan@chromium.org
Owner: ----
Status: Available (was: Assigned)
The issue is more complicated than I expected. There are many places assuming the table, rows, row-groups having the same computed 'writing-mode' regardless of the specified 'writing-mode' on rows and row-groups.

Making it available since I will have a long vacation.  
Labels: Code-ComputedStyle
Labels: ApproachableBug
Labels: -Update-Quarterly
Project Member

Comment 7 by sheriffbot@chromium.org, Dec 6

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment