Open Bug 1594278 Opened 3 months ago Updated 2 months ago

Fix usage of nsIDocShellTreeItem in nsCoreUtils::GetScreenCoordForWindow

Categories

(Core :: DOM: Navigation, defect, P2)

defect

Tracking

()

Fission Milestone M6

People

(Reporter: djvj, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [rm-docshell-tree-item:hard])

https://searchfox.org/mozilla-central/rev/8b7aa8af652f87d39349067a5bc9c0256bf6dedc/accessible/base/nsCoreUtils.cpp#319

Uses the DocShell to obtain the tree-owner, and retrieves the window from that to obtain the screen coordinates.

This should be changed to use BrowsingContext and BrowsingContextGroup and WindowContext - if in process. Window coordinates are likely too sensitive to be replicated across processes (and potentially updated too frequently), so for cases where the window is out of process, this implies some sort of IPC.

However, the IPC should only end up happening in rare cases - situations where the screen coordinates are obtained from documents which are from a different origin from the tab root document.

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

Fission Milestone: --- → ?
Fission Milestone: ? → M6
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.