- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Jan 2014 23:00:43 +0000
- To: public-pointer-events@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24346
Bug ID: 24346
Summary: Clarifications on Pointer Events Types section
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
Created attachment 1431
--> https://www.w3.org/Bugs/Public/attachment.cgi?id=1431&action=edit
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).
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 21 January 2014 23:00:44 UTC