Closed
Bug 1866173
Opened 2 years ago
Closed 1 year ago
PointerLock doesn't work on a very small oop iframe
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
FIXED
128 Branch
People
(Reporter: edgar, Assigned: edgar)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
Attachments
(2 files)
STR:
- load test.html
- click gray square
Expected result:
pointer input is locked in iframe
Actual result:
Mouse keeps being moved to top-left of browser window.
| Assignee | ||
Comment 1•2 years ago
|
||
Updated•1 year ago
|
Attachment #9365101 -
Attachment description: Bug 1866173 - Make GetWindowClientRectCenter() working properly on oop iframe; → Bug 1866173 - Make GetWindowClientRectCenter() working properly on oop iframe; r?smaug
Pushed by echen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4afa0c89126e
Make GetWindowClientRectCenter() working properly on oop iframe; r=smaug
Comment 3•1 year ago
|
||
Backed out for causing mochitest plain failures on test_pointerlock_xorigin_iframe_movementXY
Failure log:
- https://treeherder.mozilla.org/logviewer?job_id=458372669&repo=autoland
- https://treeherder.mozilla.org/logviewer?job_id=458378609&repo=autoland
Backout link: https://hg.mozilla.org/integration/autoland/rev/da6f0e3ab974044cfd6491bf003388551b773f0e
Flags: needinfo?(echen)
| Assignee | ||
Comment 4•1 year ago
•
|
||
Hmm, I think it is a pointerlock bug on Android with mouse input, I disable the test on Android for now and filed bug 1897103.
Flags: needinfo?(echen)
Pushed by echen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e0b1624713c9
Make GetWindowClientRectCenter() working properly on oop iframe; r=smaug
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
Updated•1 year ago
|
Flags: qe-verify+
Issue is reproducible on a 2024-05-15 Nightly build on Windows 10.
Verified as fixed on Firefox 128.0b1 and Firefox Nightly 129.0a1 on Windows 10, Ubuntu 22, macOS 14.
You need to log in
before you can comment on or make changes to this bug.
Description
•