This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24346 - Clarifications on Pointer Events Types section
Summary: Clarifications on Pointer Events Types section
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
Depends on:
Reported: 2014-01-21 23:00 UTC by Patrick H. Lauke
Modified: 2014-03-04 20:36 UTC (History)
2 users (show)

See Also:

markup fragment to illustrate proposed changes (5.88 KB, text/html)
2014-01-21 23:00 UTC, Patrick H. Lauke

Description Patrick H. Lauke 2014-01-21 23:00:43 UTC
Created attachment 1431 [details]
markup fragment to illustrate proposed changes

Proposed changes (see attached fragment):

- reorder the "List of pointer events" table to better reflect the typical order in which the enter/over/down/move/up/out/leave are fired

- remove "plus dispatch of compatibility mouse events" for pointerdown, as it seems misleading...most other events also fire their respective compatibility mouse event

- add note directly after table, pointing out that this is in fact the case, with internalDFN reference to "compatibility mouse events" section

- reorder the sections after the table, for each of the event types, to match the new order in the table

- in the section for "pointerdown", move the note from the end ("For mouse ... this means") right after the first paragraph, as that's where it makes the most logical sense

- add clarifications to the "Authors can prevent..." sentence in the "pointerdown" section, to explain that cancelling the event sets the PREVENT MOUSE EVENT FLAG on the pointer (so the concept is already introduced, though it will be mentioned again later), and that this does not prevent compat mouse events that may have been fired before pointerdown (for pointerover/pointerenter).
Comment 1 Rick Byers 2014-01-21 23:59:53 UTC
This looks great to me, thanks!  One minor correction, "(with the exception of pointercancel, gotpointercapture and lostpointercapture)" should be "(with the exception of gotpointercapture and lostpointercapture)".  As discussed later, pointercancel actually generates a mouseup targeted at the window.
Comment 2 Patrick H. Lauke 2014-01-22 00:19:50 UTC
Ah yes, good catch on the pointercancel.
Comment 3 Patrick H. Lauke 2014-02-11 22:04:22 UTC
Jacob, does this change need to be further discussed on list/in a call? Or is it good to go with the next round of updates?
Comment 4 Jacob Rossi [MSFT] 2014-02-25 16:40:00 UTC
Fixed as suggested in the latest spec. Good improvement!
Comment 5 Patrick H. Lauke 2014-03-04 20:36:20 UTC
second point (removing "plus dispatch [now firing] of compatibility mouse events") now split into