1450601 - [BC] borders around cells of a 'position: sticky' or 'position: relative' table row are incorrectly drawn

Status: NEW

(Core :: Layout: Tables, defect, P3)

Description

[Gérard Talbot]

This spun from bug 1450584.

Self-explanatory test
- - - - - - - - - - -

http://www.gtalbot.org/BugzillaSection/BC-border-sticky-relative-tr.html



Actual results
- - - - - - - -

Borders between cells of a 'position: sticky' or 'position: relative' table row are not drawn.

Borders around cells of a 'position: sticky' or 'position: relative' table row are incorrectly drawn.



Expected results
- - - - - - - - -

Borders between cells of a 'position: sticky' or 'position: relative' table row are drawn.

Borders around cells of a 'position: sticky' or 'position: relative' table row are drawn like in the table-row reference.


Notes
-----
- If you toggle OFF the background-color of <tr>, then Firefox 61 achieves expected results
- Chromium 64.0.3282.119 achieves expected results in both scenarios.
- Firefox 61.0a1 buildID=20180401100341 fails in both scenarios.

Comment 1

[Gérard Talbot]

I have not searched for a duplicate so far. So, marking as UNCONFIRMED for now.

Comment 2

[Gérard Talbot]

I have searched for duplicate and did not find any. Therefore, 

Marking as NEW

Comment 3

[Flaburgan]

This is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1450584

Comment 5

[Daniel Holbert [:dholbert]]

Attachment: testcase 1 (from reporter)

Comment 6

[Daniel Holbert [:dholbert]]

Attachment: testcase 2 ("selected" should always have a solid border)

Here's a testcase reduced from wpt.fyi on dupe bug 1821801.

For wpt.fyi triage mode to work properly in its current form, all of the selected cells should have a black border on all four sides. In Firefox, the border is not visible (it's behind the background, I think) on any side that has another adjacent cell.

Comment 7

[Daniel Holbert [:dholbert]]

(In reply to Flaburgan from comment #3)

This is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1450584

(Maybe, though see comment 0 and bug 1450584 comment 4; gtalbot explicitly spun this off of that very bug.)