Open
Bug 1000435
Opened 10 years ago
Updated 2 years ago
[BC] Table cell borders disappear partially with border-collapse and rowspan
Categories
(Core :: Layout: Tables, defect)
Tracking
()
NEW
People
(Reporter: frsiglmu, Unassigned)
Details
Attachments
(1 file)
10.05 KB,
application/xhtml+xml
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140421221237 Steps to reproduce: I created a huge table (roughly 20 columns x 100 rows) in which lots of cells have rowspan > 1. Via CSS I made sure these cells have visible borders and the cell borders should collapse. (I am going to attach an example file.) Actual results: Some of the cell borders are partially invisible, especially in the right half of the table. Which parts of the borders are visible and which are not seems to change when I scroll away and back again. Expected results: The borders should always be visible. Note: Bug 244135 seems to be about the same or a similar problem which was marked as "RESOLVED FIXED" in 2007, but I was asked to file a new report.
Comment 1•10 years ago
|
||
I can reproduce on Mac Nightly, but the scrolling behavior is slightly different. If I scroll and then reload, the borders change.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Table cell borders disappear partially with border-collapse and rowspan → [BC] Table cell borders disappear partially with border-collapse and rowspan
Comment 2•10 years ago
|
||
We have found the same behavior when we have added a second <tbody> to a working table with borders. We are using a colspan but no rowspan. We were using a second tbody to group rows (not nested). The borders flash on an off on random cells as you hover and/or scroll. As soon as an empty tbody was added above the existing tbody, the bug presented itself immediately.
Comment 3•2 years ago
|
||
FWIW, this is still reproducible in my Linux Nightly, though it seems to fix itself when I force a repaint by zooming in and then out (Ctrl +
and then Ctrl -
).
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•