2005205 - Initialize UsesOriginAgentClusters when restoring about:blank with content principal from session history

Status: NEW

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

Description

[Vincent Hilla [:vhilla]]

See bug 2004165, esp comment 10.

If an initial about:blank with content principal is restored from session history, EnsureUsesOriginAgentClusterInitialized might fail in the synchronous load path. As preliminary fix, we skip the synchronous path in DoURILoad in that case. We should look into fixing this properly.

Comment 1

[Vincent Hilla [:vhilla]]

We'll have to see how well the fix works. I'll mark this as S4 for now, hoping defaulting back to the async load happens rarely and causes not much problems.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 543435

Comment 3

[Donal Meehan [:dmeehan]]

Next week is the final week of nightly for Fx148.

:vhilla, what is the current status of the investigation/priority here?

Comment 4

[Vincent Hilla [:vhilla]]

It's low priority and doesn't need to block 148.

I'm not sure if this bug can impact users at all. If an about:blank is restored with a content principal for which UsesOriginAgentClusters isn't initialized, we'll do an async load. For this sync vs async behavior to have an impact, some page needs to observe the load. But

• We've only seen this with top-level about:blank and I don't think session restore would restore the window proxy or so
• The observing page would need to be same origin, but then that page load should've initialized OAC