Closed Bug 1646565 Opened 4 years ago Closed 4 months ago

dom.cross_origin_iframes_loaded_in_background is broken with Fission

Categories

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

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Project Flags:
Fission Milestone Future

People

(Reporter: kmag, Unassigned)

References

(Blocks 2 open bugs)

Details

It's supposed to allow loading iframes in the background when the parent window is from a different site, but in those cases, it will be cross-process under Fission, and will therefore never work.

Ideally we probably want the background load logic to happen before we ever create a docshell or the process in which it will live, but we can still fix this issue in the meantime.

Severity: -- → S3
Priority: -- → P3

This will need to be fixed only when we start enabling dom.cross_origin_iframes_loaded_in_background (was implemented in bug 1512388).

Fission Milestone: --- → Future

This code is turned off and broken even without Fission.

Blocks: 1512388
Summary: Fix GetInProcessParentDocshell usage in nsDocShell::CreateContentViewer → dom.cross_origin_iframes_loaded_in_background is broken with Fission

Do we have documentation around what dom.cross_origin_iframes_loaded_in_background is meant to accomplish?

The idea was to improve page load performance - cross origin iframes wouldn't block top level page load.
But IIRC it was implemented before we had good tools for vismet, so I'm not sure how much it affects those numbers.

This feature was completely removed in bug 1873967

Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.