- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jan 2022 16:01:49 +0000
- To: public-pointer-events@w3.org
I agree with @bokand. As we currently do for sticky position we should look to the nearest scroll container, which is defined to be `overflow: hidden | scroll | auto`, but not `overflow: visible | clip` per https://drafts.csswg.org/css-overflow-3/#scroll-container . Beyond making sure that touch-action can be calculated at style time, this helps ensure that we get deterministic behavior which ensures that sites don't break if for example your font is slightly too large or small or screen is the wrong size. For example, consider a shade with `touch-action: none` and popup message box containing a possibly scrollable message such as this demo: https://output.jsbin.com/tunejer. If we determine the touch action dynamically, then whether they can scroll the main page by swiping on the message box depends on whether it had overflow. Note that chrome currently have a bug with overscroll-behavior only applying to scroll containers which have overflow. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/319#issuecomment-1011196837 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 January 2022 16:01:51 UTC