Fission-aware API for getting the correct coordinates of HTML elements.
Categories
(Core :: Layout, defect, P2)
Tracking
()
People
(Reporter: ablayelyfondou, Unassigned)
References
(Depends on 1 open bug)
Details
API needed for getting the correct coordinates of an element that lives inside an oop iframe. Before fission, getElementBoundingRect was used to get those coordinates but this function relies on window.mozInnerScreenX and window.mozInnerScreenY which always return the top-level window coordinates instead of the oop iframe ones. And after a conversation with jwatt, it might not be a good idea to use that API internally anymore (see bug 1555138).
|
Reporter | |
Updated•6 years ago
|
|
||
Comment 1•6 years ago
|
||
Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
|
|
||
Comment 2•6 years ago
|
||
And after a conversation with jwatt, it might not be a good idea to use that API internally anymore (see bug 1555138).
WONTFIX because content process should not be allowed to know its screen coordinates. Parent process can map content process's document-relative coordinates to screen coordinates.
Description
•