Closed
Bug 1973691
Opened 11 months ago
Closed 10 months ago
Too many events from touch simulator on pages with same-origin iframes
Categories
(DevTools :: Responsive Design Mode, defect, P2)
DevTools
Responsive Design Mode
Tracking
(firefox142 fixed)
RESOLVED
FIXED
142 Branch
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: hbenl, Assigned: hbenl)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
STR:
- open https://hbenl.github.io/test/iframe-touch/parent.html
- enable RDM and touch simulation
- open the web console
- click on the iframe and look for messages in the console
Expected:
- one message "pointerdown from child"
- one message "touchstart from child"
- one message "mousedown from child"
Actual:
- two messages "pointerdown from child"
- two messages "touchstart from parent"
- one message "touchstart from child"
- one message "mousedown from child"
Comment 1•11 months ago
|
||
To clarify, for cross origin iframes, we have the expected number of events. DevTools might be dealing with this incorrectly because we used to have only one target per origin, but there seems to also be a platform issue where synthesized events unexpectedly bubble from frame to parent.
Severity: -- → S3
Priority: -- → P2
| Assignee | ||
Comment 2•10 months ago
|
||
Actually for cross origin iframes we also get two "pointerdown from child" messages instead of one but the "touchstart from parent" messages don't show up in that case.
| Assignee | ||
Comment 3•10 months ago
|
||
Updated•10 months ago
|
Assignee: nobody → hbenl
Status: NEW → ASSIGNED
Pushed by hbenl@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/28ebff7759af
https://hg.mozilla.org/integration/autoland/rev/9afafc2985d0
[devtools] Fix the touch simulation sending too many events. r=ochameau,devtools-reviewers
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
status-firefox142:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Updated•10 months ago
|
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in
before you can comment on or make changes to this bug.
Description
•