Bug 210656

Summary: REGRESSION (?): Safari incorrectly positions elements that have a CSS combination of display:grid and position:sticky
Product: WebKit Reporter: mohannad
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, mrobinson, simon.fraser, warnellw, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: Safari 13   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
HTML page demonstrating issue. none

mohannad
Reported 2020-04-17 08:31:37 PDT
Created attachment 396767 [details] HTML page demonstrating issue. Safari incorrectly positions sticky elements that have a CSS combination of display:grid and position:sticky - This used to work just fine in prior releases. - Please see attached HTML page. The blue box (position: sticky) should stay in the same position when scrolling vertically but once the height of the view port has been reached, the box starts moving up like a regular element.
Attachments
HTML page demonstrating issue. (9.52 KB, text/html)
2020-04-17 08:31 PDT, mohannad 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-04-17 08:32:42 PDT
<rdar://problem/61936103>
Wesley Warnell
Comment 2 2020-07-21 10:57:38 PDT
Ran into this bug today (July 21, 2020) and can confirm it is still an issue on MacOS 10.15.5 and Safari 13.1.1.
Wesley Warnell
Comment 3 2020-07-21 11:03:13 PDT
(In reply to Wesley Warnell from comment #2) > Ran into this bug today (July 21, 2020) and can confirm it is still an issue > on MacOS 10.15.5 and Safari 13.1.1. It also an issue in the latest Safari Technology Preview Release 110 (Safari 14.0, WebKit 15610.1.21.0.2) on MacOS 10.15.5.
Martin Robinson
Comment 4 2021-10-04 03:53:03 PDT
I am not seeing this issue in Safari 14 or 15. Can you confirm it's still an issue for you? There have been quite a few recent position:sticky improvements.
mohannad
Comment 5 2021-10-04 11:55:36 PDT
Correct, this behavior appears correct in the latest Safari. Thanks! I am marking this as resolved.
Note You need to log in before you can comment on or make changes to this bug.