- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Apr 2021 22:36:35 +0000
- To: public-pointer-events@w3.org
> this is new, and i don't think defined anywhere? this definitely should be added in the spec if it's supposed to be normative (and we need a test for this as well). or is it just a heuristic that blink does? No this is not new. I just tested it with Safari and Firefox and they all do the same as what Blink does today. This is what I expect from the `passive: true` in the event listener as defined in the DOM spec. Meaning that the default action of the event will run regardless of whether the handler calls preventDefault or not. So I assume we are inline with how passiveness is spec'ed already and nothing to add to PointerEvent spec. Our default action in this case I'm testing is [dispatching compat mouse events](https://w3c.github.io/pointerevents/#ref-for-dfn-compatibility-mouse-events-11:~:text=Authors%20can%20prevent%20the%20production%20of,events%20by%20canceling%20the%20pointerdown%20event.) and calling `preventDefault` does prevent it. But if we add `passive: true` mouse events continue firing despite `preventDefault`. -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/360#issuecomment-824407307 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 April 2021 22:36:39 UTC