Open Bug 1665474 Opened 4 years ago Updated 10 months ago

Implement the Origin-Agent-Cluster header

Categories

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

enhancement

Tracking

()

ASSIGNED

People

(Reporter: d, Assigned: farre)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

(Keywords: dev-doc-needed)

Severity: -- → N/A
Priority: -- → P3
Summary: Implement the Origin-Isolation header → Implement the Origin-Agent-Cluster header

Please see how this lack-of-support impacts functionality in related projects. It would be a shame if the only browser that is able to perform is Meta.

https://github.com/Igalia/wolvic/issues/46

(In reply to steve from comment #2)

Please see how this lack-of-support impacts functionality in related projects. It would be a shame if the only browser that is able to perform is Meta.

https://github.com/Igalia/wolvic/issues/46

IIUC this kind of implies that we would want to use this mainly for performance improvements, not only for enhanced security. In fact the spec says about consequences:

In terms of observable effects, this means that attempting to relax the same-origin restriction using document.domain will instead do nothing, and it will not be possible to send WebAssembly.Module objects to cross-origin Documents (even if they are same site).

And then:

Behind the scenes, this isolation can allow user agents to allocate implementation-specific resources corresponding to agent clusters, such as processes or threads, more efficiently.

So supporting this for the mandatory part might be relatively easy (to be fair, I ignore what it really takes), but having also the resource benefits might be harder. Would it be worth doing one without the other?

Flags: needinfo?(smaug)

Moving this to DOM: Navigation, though this is really cross-module thing. But I think most of the changes would be around document channel and how it selects the right process etc.

Component: DOM: Content Processes → DOM: Navigation
Flags: needinfo?(smaug)
Assignee: nobody → afarre
Status: NEW → ASSIGNED
You need to log in before you can comment on or make changes to this bug.