- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 May 2016 16:34:47 +0000
- To: public-pointer-events@w3.org
NavidZ has just created a new issue for https://github.com/w3c/pointerevents: == While pointer is captured the boundary of the capturing element should be itself and all its children == Looking at this example: https://output.jsbin.com/xidupe It shows that the hover state is active even if the mouse is over one of the children and not on the element itself. To mimic the same behavior while pointer is captured to an element if the mouse enters one of its children element it should be considered on the capturing element. Basically when the pointer is captured the meaning of pointerover/out will be the same as the meaning of pointerleave/enter instead of other way around. This is the same behavior as Edge does but it is not clear from the spec. As we discussed during the meeting I'm going to send a small fix for this to clarify that. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/62 using your GitHub account
Received on Friday, 6 May 2016 16:36:42 UTC