- From: Botond Ballo via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Apr 2020 17:50:23 +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`? I think perhaps the more interesting case (and possibly what @liviutinta was getting at) is when `#target` does not overflow `#intermediate` and `#intermediate` does not overflow `#container` either, but `#container` overflows the visual viewport. Should the `touch-action: none` prevent scrolling the visual viewport within the layout viewport in that case? A similar question [previously came up for `overscroll-behavior`](https://github.com/w3c/csswg-drafts/issues/3267), where the oucome was that there should be no special provision to preserve the ability to scroll the visual viewport within the layout viewport in a case like this. -- GitHub Notification of comment by theres-waldo Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/319#issuecomment-614800904 using your GitHub account
Received on Thursday, 16 April 2020 17:50:26 UTC