Closed Bug 1511231 Opened 4 years ago Closed 11 months ago

PointerEvent.getCoalescedEvents return empty when using pen input and while the pointer is down

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

63 Branch
defect

Tracking

()

RESOLVED FIXED
93 Branch
Webcompat Priority revisit
Tracking Status
firefox63 --- wontfix
firefox64 --- wontfix
firefox65 --- wontfix
firefox93 --- fixed

People

(Reporter: qijinz, Assigned: edgar)

References

(Blocks 2 open bugs)

Details

Attachments

(5 files)

Attached file index.html
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0

Steps to reproduce:

1. Navigate to https://qijinz.github.io/getCoalescedEvents_bug or load the attached file.
2. Draw in the red canvas with a pen input.


Actual results:

Can't draw. Only draw scratches.

e.getCoalescedEvents() on a pointermove event returns an empty list.


Expected results:

Draws. It works when using mouse input.

e.getCoalescedEvents() on a pointermove event should return at least one coalesced event (worst case the fired pointermove event itself should be returned).
Component: Untriaged → DOM: Events
Product: Firefox → Core
smaug, should this be P2 instead?
Flags: needinfo?(bugs)
pen is rarely used, hard to see why this would need to be p2.
Flags: needinfo?(bugs)
Component: DOM: Events → Event Handling
(In reply to Olli Pettay [:smaug] (high review load) from comment #2)
> pen is rarely used, hard to see why this would need to be p2.

Thanks. It wasn't clear to me what the extent of breakage is when pen *is* used.
It came up in our partner channel, so flagging for webcompat prioritization.
Flags: webcompat?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: Event Handling → User events and focus handling

See bug 1547409. Moving webcompat whiteboard tags to project flags.

Webcompat Priority: --- → ?
Webcompat Priority: ? → revisit
Assignee: nobody → echen
Blocks: 1631377
Depends on: 1725493
Pushed by echen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fa0e4e205617
Part 1: Remove unused constructor from WidgetPointerEvent; r=smaug
https://hg.mozilla.org/integration/autoland/rev/bc913eaeeff2
Part 2: Make PointerEventHandler::InitPointerEventFromTouch take references; r=smaug
https://hg.mozilla.org/integration/autoland/rev/94a5ef68aac3
Part 3: Expose coalesced Touches to PointerEvent.getCoalescedEvents(); r=smaug
https://hg.mozilla.org/integration/autoland/rev/79dc991bfa6c
Part 4: s/ProcessPendingColaescedTouchData/ProcessPendingCoalescedTouchData/; r=smaug

Backed out 4 changesets (Bug 1511231) for causing cpp bustages in CoalescedTouchData.cpp
Backout link: https://hg.mozilla.org/integration/autoland/rev/d17f970d6b32ba9d61ccc10e14f814eca4e3b0a9
Push with failures, failure log.

Flags: needinfo?(echen)
Flags: needinfo?(echen)
Pushed by echen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a63bbff6fa40
Part 1: Remove unused constructor from WidgetPointerEvent; r=smaug
https://hg.mozilla.org/integration/autoland/rev/12cdf37e494f
Part 2: Make PointerEventHandler::InitPointerEventFromTouch take references; r=smaug
https://hg.mozilla.org/integration/autoland/rev/4882bffd97f8
Part 3: Expose coalesced Touches to PointerEvent.getCoalescedEvents(); r=smaug
https://hg.mozilla.org/integration/autoland/rev/51c88c4d63a9
Part 4: s/ProcessPendingColaescedTouchData/ProcessPendingCoalescedTouchData/; r=smaug
You need to log in before you can comment on or make changes to this bug.