Closed Bug 1597443 Opened 5 years ago Closed 4 years ago

Fix uses of UpdateDocShellOrientationLock in dom/base/nsScreen.cpp

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla77
Fission Milestone M6
Tracking Status
firefox77 --- fixed

People

(Reporter: djvj, Assigned: smacleod)

References

(Blocks 1 open bug)

Details

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

In file dom/base/nsScreen.cpp

Uses DocShellTree to get same-type root of DocShell associated with incoming window.

  • Calls “SetOrientationLock” on the root docshell.

Called from Screen::mozLockOrientation web API

Root can be out-of-process.

Low-frequency event that is coarse grained and not that performance sensitive.

Convert to BrowsingContext to traverse ancestors.

  • If tree goes out of process, use IPC to forward SetOrientationLock to correct process.

Kannan says replacing nsIDocShellTreeItem calls should block enabling Fission in Nightly (M6).

Fission Milestone: --- → M6
Priority: -- → P3

It appears as though OrientationLock is android only right now, so this may not be super high priority for the initial work, but this likely could be somewhat easily handled with an OrientationLock synced field on the root BrowsingContext.

Assignee: nobody → smacleod
Status: NEW → ASSIGNED
See Also: → 1597413
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
You need to log in before you can comment on or make changes to this bug.