- From: Antoine Quint via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jun 2019 06:51:51 +0000
- To: public-pointer-events@w3.org
graouts has just created a new issue for https://github.com/w3c/pointerevents: == Setting pointer capture on an element in a parent frame when the pointer was made active in a child frame == The test [pointerevent_mouse_pointercapture_inactivate_pointer.html](https://github.com/web-platform-tests/wpt/blob/master/pointerevents/pointerevent_mouse_pointercapture_inactivate_pointer.html) specifically checks that handling a `pointerdown` event dispatched on a target element in a child frame and calling `setPointerCapture()` in the parent frame on an element contained in the parent frame should *not* trigger pointer capture. However, I'm not finding explicit text in the spec that would specify this behavior. The only step in [Setting Pointer Capture](https://w3c.github.io/pointerevents/#setting-pointer-capture) that should fails silently is: > 4. If the pointer is not in the active buttons state, then terminate these steps. But I can't see anything that specifies that, in this scenario, the pointer would not be in the active buttons state. As it stands on [wpt.fyi](https://wpt.fyi/results/pointerevents/pointerevent_mouse_pointercapture_inactivate_pointer.html?label=master&label=experimental), I see Chrome and Edge pass this test, but Firefox and Safari do not. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/291 using your GitHub account
Received on Thursday, 27 June 2019 06:51:53 UTC