Closed
Bug 1649065
Opened 4 years ago
Closed 3 years ago
Consider whether we need to call PresShell::Freeze for OOP iframes or not when the top level document is going to be in BFCache
Categories
(Core :: DOM: Navigation, task, P3)
Core
DOM: Navigation
Tracking
()
RESOLVED
DUPLICATE
of bug 1671510
Fission Milestone | M7 |
People
(Reporter: hiro, Unassigned)
References
(Blocks 2 open bugs)
Details
From bug 1592895 comment 6;
it looks like freezing is only in order to put the pres shell on the BFCache. I think we only store the presentation of the top level document, but icbw. In any case, this should probably be figured out as part of the BFCache changes for Fission.
I am guessing it should be invoked from the parent process.
Updated•4 years ago
|
Fission Milestone: --- → M6c
Updated•4 years ago
|
Severity: -- → N/A
Priority: -- → P3
Updated•4 years ago
|
Blocks: fission-bfcache
Comment 2•4 years ago
|
||
Tracking for Fission MVP. We want to enable Fission bfcache before shipping to Beta, but it doesn't necessarily block our Beta experiment (M7).
Fission Milestone: M7 → MVP
Comment 3•3 years ago
|
||
Moving BFCache bugs from Fission MVP to M7 Beta.
Fission Milestone: MVP → M7
Comment 4•3 years ago
|
||
Doesn't seem particularly useful. Everything needs to be frozen of course, and bfcache does store the presentation of all the document, including subdocuments. So, this is basically a dup of the main bfcache bug.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•