20872 2013-02-05 04:13:32 +0000 PREVENT MOUSE EVENT flag should be per pointer type 2013-02-07 02:17:51 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 jrossi jrossi public-pointer-events public-pointer-events-bugzilla oldest_to_newest 82564 0 jrossi 2013-02-05 04:13:32 +0000 > 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 82675 1 jrossi 2013-02-07 02:17:51 +0000 Made change as resolved in the 2/5 telecon: RESOLUTION: http://www.w3.org/2013/02/05-pointerevents-minutes.html#item05 https://dvcs.w3.org/hg/pointerevents/rev/851c776cffa1 https://dvcs.w3.org/hg/pointerevents/rev/4102d89c1b31