- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Thu, 09 Oct 2025 14:21:09 +0000
- To: public-css-archive@w3.org
I agree. It's a bit unfortunate that we called viewport panning scrolling (exposed via scroll events and scroll offsets on the visual viewport api) as just from the terms it sounds like it should be prevented. However from a user perspective, even if I reach the limit of a scroll container and that scroll container doesn't have any more scrolling available I shouldn't be stuck having to pinch to move the visual viewport. I propose that once we encounter an `overscroll-behavior: contain | none` element, we immediately jump to panning the visual viewport. We should still prevent browser overscroll gestures such as back navigation and pull to refresh, as this is a core use case for this API to avoid accidental back navigations in horizontal scrolling experiences. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12919#issuecomment-3386118391 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 October 2025 14:21:10 UTC