Closed Bug 1421483 Opened 7 years ago Closed 7 years ago

Using correct frame to do hit test for touchstart with multiple touches

Categories

(Core :: DOM: Events, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
mozilla59
Tracking Status
firefox59 --- fixed

People

(Reporter: stone, Assigned: stone)

Details

Attachments

(1 file)

      No description provided.
Assignee: nobody → sshih
Priority: -- → P2
Comment on attachment 8933188 [details] [diff] [review]
Using correct frame to do hit test for touchstart with multiple touches

Do you have a testcase showing this being an issue?
Or does GetEventCoordinatesRelativeTo + FindFrameTargetedByInputEvent currently anyhow end up returning the right target, as I expect.
Attachment #8933188 - Flags: review?(bugs) → review+
(In reply to Olli Pettay [:smaug] (ni?s and f?s processed after r?s) from comment #2)
> Comment on attachment 8933188 [details] [diff] [review]
> Using correct frame to do hit test for touchstart with multiple touches
> 
> Do you have a testcase showing this being an issue?
> Or does GetEventCoordinatesRelativeTo + FindFrameTargetedByInputEvent
> currently anyhow end up returning the right target, as I expect.

I found this when synthesizing a touchstart event with multiple 'new' touch instances. In that case, we use the hit frame of the first touch point as the input argument to do hit test for the second one and got null.
Pushed by sshih@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/a296cf538ee1
Using correct frame to do hit test for touchstart with multiple touches. r=smaug.
https://hg.mozilla.org/mozilla-central/rev/a296cf538ee1
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: