- From: David Bokan via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Apr 2020 17:27:55 +0000
- To: public-pointer-events@w3.org
> if it is able to be scrolled (content is big enough) Just FYI: the canonical way to say this is that "it has scrollable overflow". I.e. it's child content is larger than the box's padding rect > In Chromium we consider something scrollable only if it has the content to be scrolled (i.e. as you mentioned content is big enough). Do you see a particular issue with that? This is problematic because, in Blink, we compute the effective touch action during style recalc. We don't yet have (up-to-date) layout information at that point so we can't accurately tell whether or not `#intermetiate` actually has overflow. That seems to imply that if we want this behavior the computation must happen after layout or be performed during a touchstart. [According to bballo@](https://bugs.chromium.org/p/chromium/issues/detail?id=1031745#c15), Gecko just assumes `overflow:auto` is a scroller regardless of overflow. That seems reasonable to me - perhaps we should specify that and do the same in Blink? -- GitHub Notification of comment by bokand Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/319#issuecomment-614788889 using your GitHub account
Received on Thursday, 16 April 2020 17:27:58 UTC