Bug 233417
Summary: | touch-action doesn't prevent the Safari UI from collapsing | ||
---|---|---|---|
Product: | WebKit | Reporter: | Matt Perry <mattgperry> |
Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED MOVED | ||
Severity: | Normal | CC: | augus.dupin, bfulgham, h.dodov, ik, mattgperry, simon.fraser, tsmd57, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari 15 | ||
Hardware: | iPhone / iPad | ||
OS: | iOS 15 |
Matt Perry
https://q0j97.csb.app/
Steps to reproduce:
Scroll the page by initiating touch gesture from the green background. Page scrolls, this is expected. Scroll until the address bar disappears.
White box has "touch-action: pan-x" applied. Initiate touch gesture from the white box. Page does not scroll, this is expected.
Attempt to scroll down from white box. Page does not scroll but address bar *does* expand. This is not expected.
This breaks non-native drag gesture implementations.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Bruno Stasse
This also happens with (native) horizontal scroll containers.
It would also be great to have a way to prevent this on vertical scroll/pan-y, as it is not always desirable. This library, for instance, is broken because the viewport gets resized as a picture is being swiped up or down: https://photoswipe.com
Radar WebKit Bug Importer
<rdar://problem/85805111>
Simon Fraser (smfr)
This is controlled by MobileSafari code. The above radar tracks that issue.
Hristiyan Dodov
I recently ran into this issue as well. In case more info is required, here's a Stack Overflow question:
https://stackoverflow.com/questions/71717565/prevent-ios-safari-from-animating-its-address-bar-when-touch-action-none-is-used
Also a reproduction site:
https://safari-touch-action-bug.netlify.app/
And a demo video of the problem:
https://www.youtube.com/shorts/RJAQp4YO4gg
Sam Sneddon [:gsnedders]
rdar://86966949
Sam Sneddon [:gsnedders]
This is being addressed within Safari, not WebKit.
Brent Fulgham
We believe that this bug was fixed in the iOS 16.0 Beta 1 (and newer).
Hristiyan Dodov
(In reply to Brent Fulgham from comment #7)
> We believe that this bug was fixed in the iOS 16.0 Beta 1 (and newer).
I just tested on iOS 16.0.3 (20A392) and the issue is fixed.