Closed Bug 1302260 Opened 8 years ago Closed 8 years ago

Do not prerender if window.opener is non-null

Categories

(Core :: DOM: Core & HTML, defect, P3)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1315105

People

(Reporter: ehsan.akhgari, Unassigned)

References

(Blocks 1 open bug)

Details

It seems like Chrome avoids prerendering if the page has an opener, and we should do the same for OOP prerendering.
Comment 0 and the title seem at odds. Which is right?
Flags: needinfo?(ehsan)
Summary: Do not prerender if window.opener is null → Do not prerender if window.opener is non-null
Flags: needinfo?(ehsan)
Priority: -- → P3
I imagine that the technique which we use for identifying whether there are windows which could observe a page switching processes could be made to be the same as what I am using for responding to the Large-Allocation header in bug 1304140. That technique is to count the number of toplevel windows in the active TabGroup, and reject the cross process navigation if there are other toplevel windows than the active one.
This is handled by the TabGroup logic in bug 1315105
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.