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

Issue 793310 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Incorrect tbody border rendering

Reported by kriszti...@gmail.com, Dec 8 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
Added table with border-collapse: collapse, set border to tbody with 2 table rows inside. First row has multiple tds, second table row has a single td which does not have colspan (i.e., does not stretch to the full width of tbody).

What is the expected behavior?
The tbody should have a rectangular border (on all sides). This is how it works in Mac Safari and Firefox.

What went wrong?
Tbody only has border in those areas where it has child elements, border bottom and border right is missing where the td in the second table row does not stretch full width. (one screenshot is from Chrome, one is from Firefox)

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 63.0.3239.84  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
table_bug.html
501 bytes View Download
Screen Shot 2017-12-08 at 15.51.00.png
8.7 KB View Download
Screen Shot 2017-12-08 at 15.51.45.png
9.9 KB View Download
Components: Blink>Paint
Cc: pbomm...@chromium.org chrishtr@chromium.org gov...@chromium.org
Labels: M-64 M-65 Needs-Bisect OS-Linux OS-Windows
Able to reproduce the issue on current and previous Chrome stable i.e., 63.0.3239.84 and 62.0.3202.94 respectively. Also observing similar behavior on latest Chrome Dev(64.0.3278.0) and Canary as well.

Note : 
I see similar behavior on Edge,where in firefox and safari borders are rendered correctly.

Tagging the bug with M64 and M65, Since the issue is present on M62.
Status: Untriaged (was: Unconfirmed)
Cc: wangxianzhu@chromium.org
I think this is likely to be a regression. We've made many changes to collapsed
borders in the last year.
Labels: -Pri-2 -M-65 -M-64 Pri-3
Not a regression. I reproduced it on r100008 (before blink branch).

We calculate collapsed borders by cells, so there will be no collapsed border around the area containing no cells. The CSS 2.1 spec doesn't specify how to deal with such situation.
Cc: dgro...@chromium.org robhogan@chromium.org
Components: -Blink>Paint Blink>Layout>Table
Labels: -Needs-Bisect
Found the following statement in https://www.w3.org/TR/CSS2/tables.html:

"
A "missing cell" is a cell in the row/column grid that is not occupied by an element or pseudo-element. Missing cells are rendered as if an anonymous table-cell box occupied their position in the grid.
"

So one way might be to create anonymous LayoutTableCells for "missing cells".

However, it seems that no browser follows this exactly. For example, http://jsbin.com/jabivop, all browsers don't paint the bottom-right missing cell. According to the above statement, the bottom-right "missing cell" should paint a yellow background as if there were a cell.

Moving to Blink>Layout>Table because the candidate solution is about anonymous cells in layout tree for missing cells .

Another thing I noticed is that if there is a cell in a row with higher colspan then the number of cells in the previous row, it also breaks the border rendering on the tbody element (not sure if it's related or should be treated as a separate issue)
colspan_border.html
477 bytes View Download

Comment 8 by e...@chromium.org, Dec 13 2017

Status: Available (was: Untriaged)
Project Member

Comment 9 by sheriffbot@chromium.org, Dec 14

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
Cc: -robhogan@chromium.org robho...@gmail.com
Status: Available (was: Untriaged)

Sign in to add a comment