RDM with touch events sends SetCapture warning in the console
Categories
(DevTools :: Responsive Design Mode, defect, P3)
Tracking
(firefox130 fixed)
Tracking | Status | |
---|---|---|
firefox130 | --- | fixed |
People
(Reporter: karlcow, Assigned: nchevobbe)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
What were you doing?
- Open Firefox, activate RDM with a Mobile UA and touch activated.
- Go to https://www.mozilla.org/en-US/
- Click on a link.
What happened?
The following message appears in the console.
Element.setCapture() is deprecated. Use Element.setPointerCapture() instead. For more help https://developer.mozilla.org/docs/Web/API/Element/setPointerCapture
What should have happened?
Nothing probably
which is calling
Anything else we should know?
Probably not urgent.
Updated•3 years ago
|
Comment 2•2 years ago
|
||
We've received a report in https://github.com/webcompat/web-bugs/issues/107300 about this issue. The warning message could be misleading for developers as it makes you believe that the issue is with the actual code and not RDM.
Assignee | ||
Comment 7•4 months ago
|
||
The message was added in Bug 777972 (see https://hg.mozilla.org/mozilla-central/diff/8b82a374ece51b3d874bbc41db97ef5b2e0c5026/browser/devtools/shared/touch-events.js)
evt.target.setCapture
was used to make sure events are not dispatched to something else, for example a different window.
We could replace this with evt.target.setPointerCapture, but there is no test covering this, and trying to make appear an overlapping
element still only dispatch the element to the original target, so we can probably remove this just fine.
Assignee | ||
Comment 8•4 months ago
|
||
evt.target.setCapture is deprecated and displays a message to the console.
it was used to make sure events are not dispatched to something else, for
example a different window.
We could replace this with evt.target.setPointerCapture,
but there is no test covering this, and trying to make appear an overlapping
element still only dispatch the element to the original target, so we can
probably remove this just fine.
Updated•4 months ago
|
Comment 10•4 months ago
|
||
bugherder |
Description
•