- From: David Bokan via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Apr 2020 17:36:24 +0000
- To: public-pointer-events@w3.org
> Now let's say that #target has content that is bigger than the screen (on a mobile phone). It does not overflow the #intermediate div. Should we allow default touch behaviour in this case? I tested on both Chrome and Firefox and I can scroll. Is that the correct behaviour based on the spec? So in this case `#target` doesn't overflow `#intermediate` but `#intermediate` overflows `#container`? Based on Blink's current implementation that shouldn't work, `#intermediate` doesn't have overflow so we have to look all the way up to `#container` to compute the touch behavior which will see `touch-action:none`. I'm guessing it does work because the stale layout data is actually correct so we see `#intermediate` as scrollable but we could carefully setup a case where it fails. As Gecko's behavior is to always treat `overflow:auto` as a scroller, we'd only look up to `#intermediate` to compute the touch behavior so scrolling should be allowed and that explains what you're seeing. -- GitHub Notification of comment by bokand Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/319#issuecomment-614793620 using your GitHub account
Received on Thursday, 16 April 2020 17:36:26 UTC