Bug 199990

Summary: position:sticky Chrome bug tracker header seems broken when scrolling
Product: WebKit Reporter: Myles C. Maxfield <mmaxfield>
Component: Layout and RenderingAssignee: Simon Fraser (smfr) <simon.fraser>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, rniwa, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: BrowserCompat, InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Video
none
Testcase none

Myles C. Maxfield
Reported 2019-07-21 10:32:14 PDT
See attached video. https://bugs.chromium.org/p/chromium/issues/detail?id=800693
Attachments
Video (7.68 MB, video/quicktime)
2019-07-21 10:32 PDT, Myles C. Maxfield 		no flags
Details
Testcase (615 bytes, text/html)
2019-07-22 21:14 PDT, Simon Fraser (smfr) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Myles C. Maxfield
Comment 1 2019-07-21 10:32:42 PDT
Created attachment 374571 [details] Video
Simon Fraser (smfr)
Comment 2 2019-07-22 11:45:59 PDT
It's position:sticky.
Radar WebKit Bug Importer
Comment 3 2019-07-22 11:46:13 PDT
<rdar://problem/53408604>
Simon Fraser (smfr)
Comment 4 2019-07-22 21:14:19 PDT
Created attachment 374673 [details] Testcase Seems to happen because the sticky element is enclosed in a display:inline element.
Simon Fraser (smfr)
Comment 5 2019-07-22 21:19:36 PDT
Actually any element between the root and the sticky break it.
Simon Fraser (smfr)
Comment 6 2019-07-22 21:36:43 PDT
We're considering the anonymous block ancestor as the containing block, but the other browser don't.
Simon Fraser (smfr)
Comment 7 2019-07-22 21:37:08 PDT
(In reply to Simon Fraser (smfr) from comment #5) > Actually any element between the root and the sticky break it. Ah, in all browsers. It breaks only in WebKit if the ancestor is inline.
Ahmad Saleem
Comment 8 2022-08-29 03:36:22 PDT
I am unable to reproduce this bug in Safari Technology Preview 152, where the sticky header got stuck in viewport below its position. It is behaving same as other browsers (Chrome Canary 107 and Firefox Nightly 106). I am going to mark this as "RESOLVED CONFIGURATION CHANGED". Please reopen with updated test case, if you think it is not fixed. Thanks!
Note You need to log in before you can comment on or make changes to this bug.