- From: Kagami Sascha Rosylight via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jul 2022 17:06:57 +0000
- To: public-pointer-events@w3.org
saschanaz has just created a new issue for https://github.com/w3c/pointerevents: == Order of pointerover/enter/move and corresponding mouse events is different on Firefox/Chrome == `data:text/html,<input id=input><script>input.onpointerenter = input.onmouseenter = input.onpointerleave = input.onmouseleave = input.onpointerover = input.onmouseover = input.onpointerout = input.onmouseout = input.onpointermove = input.onmousemove = ev =>console.log(ev.type)</script>` When hovering over the input, the console output is: Chrome: pointerover->pointerenter->mouseover->mouseenter->pointermove->mousemove->pointerout->pointerleave->mouseout->mouseleave Firefox: pointerover->pointerenter->->pointermove->mouseover->mouseenter->mousemove->pointerout->pointerleave->mouseout->mouseleave Somehow the timing that pointermove and mousemove appear is different. * The pointer/mousemove happens immediately on pointerenter on both Firefox and Chrome * Events are somehow grouped on both of them (pointerover+pointerenter always happen together without a compatibility event between it, for example) * And the grouping behavior is different. I'm not quite sure this grouping is specced. https://w3c.github.io/pointerevents/#mapping-for-devices-that-support-hover looks like it doesn't even give the mapping for over/enter/out/leave. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/454 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 July 2022 17:06:59 UTC