- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Jun 2015 17:59:40 +0000
- To: public-pointer-events@w3.org
RByers has just created a new issue for https://github.com/w3c/pointerevents: == setPointerCapture should say something about iframes == The [algorithm for setPointerCapture](https://w3c.github.io/pointerevents/#setting-pointer-capture) says nothing about different iframes. If, for example, code running in some iframe happens to call setPointerCapture for a pointer ID that would otherwise have its events sent to another frame, then setPointerCapture should presumably fail somehow (eg. to prevent input stealing). How exactly should this fail? What about more subtle scenarios? Eg. if I mouse down over one frame, can it capture events so that when I drag out of that frame events consider to go to it? Also, Is there any reason to prevent a child frame from explicitly directing capture to ancestor frame somehow? I've seen sites do this today by delegating all events inside a child into their parent via postMessage (eg. to allow dragging on a window resize handle within the frame to resize the frame). See https://github.com/w3c/pointerevents/issues/16
Received on Monday, 22 June 2015 17:59:41 UTC