Closed Bug 1490928 Opened 6 years ago Closed 6 years ago

PointerEvents: `pen` events become `touch` events when the pen is down and active. In such cases, `event.pressure` is always 0.

Categories

(Firefox :: Untriaged, defect)

63 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1487509

People

(Reporter: swadicalrag, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180906162647 Steps to reproduce: I attached an event listener to pointermove to log its output, and started moving my pen. Condensed test case: ``` <script> document.addEventListener("pointermove",(e) => console.log(e.pointerType,e.pressure)) </script> ``` Actual results: When my pen was hovering, the eventlistener correctly outputted the pointer type as "pen", but when my pen was down, the eventlistener outputted that the pointer type was "touch". Weirdly enough, the `event.pointerId` remains the same between these two events. This issue is reproducible in Firefox Nightly 64.0a1 (2018-09-12) (64-bit) and Firefox Developer Edition 63.0b4 (64-bit) (wacom intuos pro). This issue is also reproducible on another machine (surface pro 3 w/ surface pen) running Firefox Developer Edition 63.0b4 (64-bit). Expected results: When my pen was down, the eventlistener should have continued to output the event type as "pen", and also give me the "pressure" values of the pen. This happens correctly in Chrome 68.0.3440.106 and even Microsoft Edge 42.17134.1.0. There is no reason for my pen's pointerevent to change into a "touch" type pointerevent at all.
This seems to be a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1487509 and a bug caused by a regression in https://bugzilla.mozilla.org/show_bug.cgi?id=1345398 Setting `dom.w3c_pointer_events.dispatch_by_pointer_messages` to true in my browser seems to resolve this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.