179379 2017-11-07 10:49:07 -0800 scroll-padding should affect scrollIntoView, paging etc even when snapping is off 2021-03-12 17:32:46 -0800 1 1 1 Unclassified WebKit Scrolling WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED BrowserCompat, InRadar P2 Normal --- 219073 219074 218115 1 simon.fraser webkit-unassigned 709922234 alex charlie.croom diane.ko julien.roncaglia kyle.bavender lfloyd mqr5815 mrobinson simon.fraser steffen.weber v webkit-bug-importer wenson_hsieh oldest_to_newest 1369068 0 simon.fraser 2017-11-07 10:49:07 -0800 See https://drafts.csswg.org/css-scroll-snap/#scroll-padding 1642538 1 webkit-bug-importer 2020-04-16 18:52:02 -0700 <rdar://problem/61915456> 1676589 2 diane.ko 2020-07-30 15:24:57 -0700 From the CSS spec definition for scroll-padding (https://www.w3.org/TR/css-scroll-snap-1/#scroll-padding), scroll-padding should apply to any scroll container, not just scroll snap containers. This issue is particularly problematic when using scroll-padding to adjust for any fixed content (for example, a fixed header or footer). This behavior exists on both iOS and macOS Safari, but not on Chrome or Firefox. Note: this is particularly problematic when using iOS with VoiceOver on, as VoiceOver will trigger tapping on the location where its focus is, which means that if you're focused on an element that's underneath a fixed container, the click event will trigger on the fixed container and not the element that gets read out as having focus. As this issue isn't a problem in Chrome, I was able to successfully avoid this issue on an Android device with TalkBack enabled. I created a really basic codepen (https://codepen.io/backwardok/pen/6980c6068b69618a90bd5b12716dde8b) that demonstrates this problem (full page version: https://cdpn.io/backwardok/debug/6980c6068b69618a90bd5b12716dde8b). 1676599 3 simon.fraser 2020-07-30 15:36:48 -0700 Thanks for the testcase! 1715272 4 simon.fraser 2020-12-16 17:06:49 -0800 Martin, can we consider this fixed? 1715367 5 mrobinson 2020-12-17 04:18:37 -0800 The main blocker here is to implement the part of scroll-padding that affects scrolling area paging behavior. I don't think this should be a lot of work, but I've been dragging my feet a bit here. 1719679 6 mqr5815 2021-01-14 13:15:21 -0800 This is a major blocker to site authors implementing sticky-position banners; there is seemingly no alternative that works across the various use cases out there; for example, a common CSS approach (negatively absolute positioned generated content) does not work if the fragment refers to a replaced element like an <input>. And Safari is the only major browser that does not properly support this feature. I'm hoping this comment can serve as a +1 on prioritizing this bug. 1728517 7 mrobinson 2021-02-12 03:04:26 -0800 *** Bug 219072 has been marked as a duplicate of this bug. ***