Closed
Bug 1609798
Opened 4 years ago
Closed 4 years ago
Move useRemoteSubframes property from DocShell to BrowsingContext
Categories
(Core :: DOM: Navigation, task, P2)
Core
DOM: Navigation
Tracking
()
RESOLVED
DUPLICATE
of bug 1616353
People
(Reporter: mccr8, Unassigned)
References
(Blocks 1 open bug)
Details
Right now, this property is on doc shells, but Nika (I think) suggest it would be convenient to also be able to read the value off of the browsing context.
|
||
Updated•4 years ago
|
Priority: -- → P3
|
||
Comment 2•4 years ago
|
||
kmag says we should also remove the useRemoteSubframes property from DocShell. We want new code to use BrowsingContext, not DocShell.
M6a
Severity: normal → S3
Type: defect → task
Fission Milestone: M6 → M6a
Priority: P3 → P2
Summary: Add useRemoteSubframes property to browsing context → Move useRemoteSubframes property from DocShell to browsing context
|
|
||
Updated•4 years ago
|
Summary: Move useRemoteSubframes property from DocShell to browsing context → Move useRemoteSubframes property from DocShell to BrowsingContext
This was done in bug 1616353. DocShell now queries its BrowsingContext for useRemoteSubframes (and other nsILoadContext attributes): https://searchfox.org/mozilla-central/rev/35b97af64a55d1d30caa4d6e9fabc1a7fbabc509/docshell/base/nsDocShell.cpp#1540-1544
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
|
|
||
Comment 4•4 years ago
|
||
Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.
Fission Milestone: M6a → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•