Bug 255593

Summary:

[css-scroll-snap] refresh on page with scroll-snap on html fails

Product:

WebKit

Reporter:

Johannes Odland <johannes.odland>

Component:

Scrolling

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Major

CC:

simon.fraser, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

Safari 16

Hardware:

iPhone / iPad

OS:

iOS 16

See Also:

https://bugs.webkit.org/show_bug.cgi?id=245722
https://bugs.webkit.org/show_bug.cgi?id=255592
https://bugs.webkit.org/show_bug.cgi?id=255646

Attachments:

Description	Flags
Video of the bug	none

Johannes Odland

Reported 2023-04-18 05:35:51 PDT

Created attachment 465960 [details] Video of the bug Refreshing on a page with scroll-snap on html fails. The viewport gets stuck in the negative overflow area above the ICB. The user has to forcibly scroll down to get back to the page. If the user uses VoiceOver they are stuck. Steps to reproduce: Steps to reproduce: 1. Open a page with scroll-snap on root (https://johannesodland.github.io/browserbugs/safari-scroll-snap-scroll-to-top-issue.html) 2. Scroll down so that the viewport snaps to a position further down on the page 3. Refresh the page Expected result: The page is refreshed and the user can continue to interact with the refreshed version. Actual result: The page is refreshed, but the scroll position of the viewport is above the actual page so that the page can not be accessed. The user can scroll down to the page if they try. If the user uses VoiceOver they can not navigate the page.

Attachments
Video of the bug (1.84 MB, video/mp4) 2023-04-18 05:35 PDT, Johannes Odland	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2023-04-18 09:54:40 PDT

<rdar://problem/108206227>

Johannes Odland

Comment 2 2023-05-22 04:17:38 PDT

Retested on iOS Safari 16.5. I can no longer reproduce the issue.

Simon Fraser (smfr)

Comment 3 2023-05-22 09:15:41 PDT

Thank you for testing.

Note You need to log in before you can comment on or make changes to this bug.