Re: [pointerevents] Setting pointer capture on an element in a parent frame when the pointer was made active in a child frame (#291)

@graouts You are right. It is not very clear how the active button state is defined with respect to the iframes. But how do you feel about the current behavior?

A little background on this. We realized if we had cross origin frames we didn't want the embedder or the embedded iframe call the setpointercapture if they didn't receive an active button state pointer before for security reasons. Not only that if they had received a leave event (like when pointer leaves their boundaries) we still didn't want them to be able to capture. So we thought we should not let the element that belongs to a document that doesn't have an active pointerevent in it be able to call capture. If we accept such a logic this test should also fail. As it really doesn't matter who is calling capture on the element in the embedder. Either a timeout or a function call from the inner frame. However, let's first see what you think about the behavior in general. @graouts do you think that is reasonable? @smaug---- in case this was missed before, what do you think?

-- 
GitHub Notification of comment by NavidZ
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/291#issuecomment-507720255 using your GitHub account

Received on Tuesday, 2 July 2019 15:10:48 UTC