- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Feb 2014 13:18:58 +0000
- To: public-pointer-events@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24783 Bug ID: 24783 Summary: non-normative examples for event sequences to be added to end of 11.2 Product: PointerEventsWG Version: unspecified Hardware: PC OS: Windows NT 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 Created attachment 1439 --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1439&action=edit HTML version of proposed note As per the discussion on the list, I'd propose this additional non-normative example note at the end of 11.2 to better illustrate the kind of event sequence authors can expect to get for touchscreen taps (as Rick said, probably the most complex case that may cause the most confusion). Attached as HTML, but for ease: Example This section is non-normative. Based on the outlined algorithm, a tap with a single finger (meaning this is a primary pointer) on a touchscreen will produce the following series of pointer events and compatibility mouse events (also listing the click event, to clarify that this is fired at the very end of sequence): 1 mousemove 2 pointerover 3 mouseover 4 mouseenter 5 pointerdown 6 mousedown 7 gotpointercapture 8 (zero or more pointermove and mousemove events, depending on movement of the finger during the tap) 9 pointerup 10 mouseup 11 lostpointercapture 12 pointerout 13 mouseout 14 mouseleave 15 click. If compatibility mouse events are being suppressed by cancelling the pointerdown event, the sequence of event for the same action will be: 1 mousemove 2 pointerover 3 mouseover 4 mouseenter 5 pointerdown 6 gotpointercapture 7 (zero or more pointermove events, depending on movement of the finger during the tap) 8 pointerup 9 lostpointercapture 10 pointerout 11 mouseout 12 mouseleave 13 click -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 24 February 2014 13:19:00 UTC