RESOLVED DUPLICATE of bug 94128 128486
Table elements with position:sticky have borders repainted incorrectly on scroll 
https://bugs.webkit.org/show_bug.cgi?id=128486
Summary Table elements with position:sticky have borders repainted incorrectly on scroll
Blaze Burg
Reported 2014-02-08 20:35:40 PST
When scrolling, the background of a position:sticky table row element is painted correctly as if it were position:fixed, but the row's borders follow the scrolled table contents. In my testing, any of thead, th, td, tr with position:-webkit-sticky exhibit this bug. Other elements (divs, etc) draw borders correctly.
Attachments
testcase with position:sticky thead (1.90 KB, text/html)
2014-02-08 20:36 PST, Blaze Burg 		no flags
Details
reduced test case (283 bytes, text/html)
2014-02-08 21:34 PST, zalan 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Blaze Burg
Comment 1 2014-02-08 20:36:11 PST
Created attachment 223602 [details] testcase with position:sticky thead
zalan
Comment 2 2014-02-08 21:34:41 PST
Created attachment 223607 [details] reduced test case
Derk-Jan Hartman
Comment 3 2014-03-13 06:13:51 PDT
I suspect dupe of bug 94128
Derk-Jan Hartman
Comment 4 2017-03-29 08:14:32 PDT
3 years later, still a problem. https://en.wikipedia.org/wiki/List_of_Space_Shuttle_missions?withCSS=MediaWiki:Gadget-StickyTableHeaders.css The table headers here loose there borders whenever position sticky is used.
Blaze Burg
Comment 5 2017-03-29 10:04:20 PDT
*** This bug has been marked as a duplicate of bug 94128 ***
Simon Fraser (smfr)
Comment 6 2017-03-29 11:13:14 PDT
Does this only happen on Retina displays?
Derk-Jan Hartman
Comment 7 2017-03-29 23:18:07 PDT
@simon I just tested. No it happens on both Retina and non-Retina. Im also much less sure that this is an actual duplicate of 94128 btw. This seems much more likely to be a side effect of border collapse.
Radar WebKit Bug Importer
Comment 8 2017-04-07 19:18:02 PDT
<rdar://problem/31516367>
Yeshar
Comment 9 2018-08-21 13:33:44 PDT
This issue persists on Chrome. Not sure why it's listed as resolved. I'm guessing that people have come up with workarounds over the 4+ years this has been a bug... Any suggestions would be welcomed. :)
Derk-Jan Hartman
Comment 10 2018-08-23 01:41:29 PDT
I also don't think this is the same bug as the one it was closed as a dupe of. As far as I understand, this bug occurs due to border collapsing.
Note You need to log in before you can comment on or make changes to this bug.