- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 May 2016 16:38:09 +0000
- To: public-pointer-events@w3.org
The following commits were just pushed by RByers to https://github.com/w3c/pointerevents: * Made mouseover/out/enter/leave event firing independent of corresponding PEs (#56) The spec currently suggests that compatibility mouse transition events (i.e. mouseover, mouseout, mouseenter and mouseleave) should be fired right after firing the corresponding PointerEvents, implying a 1:1 correspondence between the PointerEvents vs the compatibility MouseEvents. This 1:1 correspondence breaks the consistency of MouseEvent sequence itself when two or more primary pointers (of different types) are active at the same time. For example, mouseover events can be sent to two different targets without a mouseout in-between, which can possibly break the UIs based on legacy MouseEvents, e.g., by opening two menu items at the same time. (Issue This patch fixes the problem by omitting the 1:1 correspondence altogether. More precisely, it suggests to fire the compatibility mouse transition events right before a pointerdown/up/move event. In addition, this patch modifies the default actions of pointerover, pointerout, pointerenter and pointerleave events to "none". This keeps the spec effectively unchanged since the original default action was "the default action of corresponding MouseEvent" but the UI Event Spec defines those default actions as "none". by Mustaq Ahmed https://github.com/w3c/pointerevents/commit/9500cf65ea7c1d7ec76169a3742764091585379a
Received on Wednesday, 25 May 2016 16:38:11 UTC