- From: <bugzilla@jessica.w3.org>
- Date: Wed, 22 Jan 2014 00:16:54 +0000
- To: public-pointer-events@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24348 Bug ID: 24348 Summary: pointerdown/pointerup/pointercancel on non-hover devices Product: PointerEventsWG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: Pointer Events specification Assignee: jrossi@microsoft.com Reporter: redux@splintered.co.uk QA Contact: public-pointer-events-bugzilla@w3.org CC: public-pointer-events@w3.org In the current spec, pointerdown/pointerup/pointercancel on input devices that do not support hover MUST fire a pointerover/pointerout/pointerout (respectively, before in the first case and after in the other two cases). pointerenter/pointerleave should also be added. Proposed changes: - "5.2.2 The pointerdown event" Currently: "For input devices that do not support hover, a user agent must also fire a pointerover event preceding the pointerdown event." Change to: "For input devices that do not support hover, a user agent must also fire a pointerover and pointerenter event preceding the pointerdown event." - "5.2.3 The pointerup event" Currently: "For input devices that do not support hover, a user agent must also fire a pointerout event after firing the pointerup event." Change to: "For input devices that do not support hover, a user agent must also fire a pointerout and pointerleave event after firing the pointerup event." - "5.2.4 The pointercancel event" Currently: "A user agent must also fire a pointerout event after firing the pointercancel event." Change to: "A user agent must also fire a pointerout and pointerleave event after firing the pointercancel event." [Incidentally, should there be something here about pointercancel generally not being applicable to input devices that DO support hover?] -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 22 January 2014 00:16:55 UTC