Open Bug 1594278 Opened 1 year ago Updated 5 months ago

Audit nsIDocShellTreeItem usage in nsCoreUtils::GetScreenCoordsForWindow


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




Fission Milestone Future


(Reporter: djvj, Unassigned)


(Blocks 1 open bug)


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

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:


Fission Milestone: --- → ?
Fission Milestone: ? → M6
Priority: -- → P2

Please audit this use of the nsIDocShellTreeItem interface. With Fission enabled, Documents and nsDocShells for related frames, such as subframes and parent documents, may not be available within the current process and the corresponding nsIDocShellTreeItem methods will return null

If this code works as-is with Fission, we don't need to remove this usage of nsIDocShellTreeItem until when we remove nsIDocShellTreeItem entirely (bug 1607591) after we ship Fission MVP.

Fission documentation about replacing nsIDocShellTree Item:

:farre's presentation with examples of replacing nsIDocShellTreeItem with BrowsingContext, WindowContext, SyncedContexts, and BrowsingContextGroup:

Summary: Fix usage of nsIDocShellTreeItem in nsCoreUtils::GetScreenCoordForWindow → Audit nsIDocShellTreeItem usage in nsCoreUtils::GetScreenCoordForWindow

Auditing whether this use of nsIDocShellTreeItem breaks when Fission is enabled blocks Fission Nightly.

Fission Milestone: M6 → M6b
Summary: Audit nsIDocShellTreeItem usage in nsCoreUtils::GetScreenCoordForWindow → Audit nsIDocShellTreeItem usage in nsCoreUtils::GetScreenCoordsForWindow

Nika said getting tree owner isn't necessarily broken.

Type: defect → task
Fission Milestone: M6b → Future
You need to log in before you can comment on or make changes to this bug.