1876213 - Removing element during pointerdown event stops all pointermove events

Status: RESOLVED DUPLICATE of bug 1695574

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

Description

[Sam Burba]

Attachment: index.html

Steps to reproduce

1. Open the attached HTML file in Firefox for Android
2. Touch the red square and drag your finger around

Expected behavior

Diagnostic element updates with pointer position as your finger drags around

Actual behavior

Diagnostic element continues to say "No pointer moves detected"

Device information

• Firefox version: 121.1.0 (Build #2015996455) 62d5117f79+
• Android device model: Google Pixel 7
• Android OS version: 14

Any additional information?

The core of the issue is if you remove the target element of a pointerdown event while handling said pointerdown event, no more pointermove events are sent, regardless of what element the pointermove event handler is registered on. Delaying the removal of the element by only removing it after window.setTimeout with a delay of 0 causes pointermove events to be fired properly.

I thought it might have to do with Implicit Pointer Capture, but explicitly calling releasePointerCapture on the element has no effect on behavior in any browser.

I've tested this in desktop and mobile Firefox, Chrome, and Safari, on a few devices and several operating systems.
It does not reproduce on any browser except Firefox for Android. It also does not reproduce when using the touch simulation feature in the Firefox dev tools on the desktop.

Comment 1

[Sam Burba]

I forgot to note, once you pick up your finger and put it down after touching the red square, pointermove events fire correctly again. You will have to refresh the page to get the red square back and reproduce the issue again.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:amejia, could you have a look please?

For more information, please visit BugBot documentation.

Comment 3

[Hiroyuki Ikezoe (:hiro)]

Now I believe the underlying issue of this bug is same as bug 1695574. FWIW, locally I confirmed D202811 fixes this bug too.

Comment 4

[Andreas Farre [:farre]]

Masayuki, do you agree?

Comment 5

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Yeah, should be. Our event handler stops dispatching following evevns once the target of pointerdown event whose input source is a touch device is reframed or removed.