- From: <bugzilla@jessica.w3.org>
- Date: Tue, 05 Feb 2013 04:13:32 +0000
- To: public-pointer-events@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20872
Bug ID: 20872
Summary: PREVENT MOUSE EVENT flag should be per pointer type
Classification: Unclassified
Product: PointerEventsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Pointer Events specification
Assignee: jrossi@microsoft.com
Reporter: jrossi@microsoft.com
QA Contact: public-pointer-events-bugzilla@w3.org
CC: public-pointer-events@w3.org
> Upon re-reading the current draft, I have a few questions.
>
> 1. At any point in time, how many pointers can simultaneously have isPrimary
set to true? The way I read it, there could be up to three, one for a mouse
device, one for a touch input, and one for a pen input, if the underlying
platform supports all three input types simultaneously. Is that correct?
Correct. Generally, users don't mix input simultaneously. In IE10, multiple
primary pointers effectively "fight" for a mouse cursor (e.g. you'll see
mousemove events firing back and forth between the two locations).
> 2. If my understanding in #1 is correct, then in "8.1 Mapping for devices
that support hover", there should be *three* different PREVENT MOUSE EVENT
flags, one for each input type. Otherwise, cancelling the pointerdown event
of the primary touch input would inadvertently disable the compatibility
mouse events for subsequent events from the primary mouse and pen inputs as
well.
Though I think I'll update this to say "set the PREVENT MOUSE EVENT flag for
this pointer type" and "if the PREVENT MOUSE EVENT flag is set for this pointer
type." That way the principle applies if new device types are added.
http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0057.html
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 5 February 2013 04:13:33 UTC