W3C home > Mailing lists > Public > public-pointer-events@w3.org > April to June 2017

Re: [pointerevents] Clarify what touch-action allows with rotated scrollable elements

From: Rick Byers via GitHub <sysbot+gh@w3.org>
Date: Wed, 26 Apr 2017 20:50:06 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-297537046-1493239805-sysbot+gh@w3.org>
> I would rather be consistent between divs and iframes, so use "client" coordinate space. 

I think this is normally called "local" co-ordinate space, right?  I.e. this is NOT what `clientX` and `clientY` events do (they are unaffected by rotated DIVs, just rotated iframes) IIRC.  I think the non-standard `MouseEvent.layerX/layerY` properties may behave this way.

Can someone verify what Edge and FF do in the case of a rotated DIV?  Does touch-action operate in client or the element-local co-ordinate space?

In particular if Edge and FF are both really using the client co-ordinate space today then I'd rather spec/test it that way.  Yes in theory there could be a problem within a frame, but that problem exists for co-ordinates generally - the code rotating something needs to also apply the same rotation to any client co-ordinate handling (and can probably do so because it's all in the same frame).  Only the iframe case is really unsolvable IMHO (because the code that knows about the transform in the parent frame doesn't necessarily have access to the events being delivered to the child frame).  Implementing the local version is probably harder for chromium than implementing the client version.  But if at least one other browser has really already implemented local as @staktrace described, then I'm OK saying Chrome just has a bug here for now.

-- 
GitHub Notification of comment by RByers
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/115#issuecomment-297537046 using your GitHub account
Received on Wednesday, 26 April 2017 20:50:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 26 April 2017 20:50:13 UTC