Re: [w3ctag/design-reviews] Deprecating `document.domain`. (#564)

I agree completely that Chromium, at least, would implement this as the tri-state enum you spell out, as I don't think we'll initially be capable of supporting process-isolated agent clusters for all origins, all the time, without performance impact. Over time, I expect we'd be able to make it boolean (or remove the header altogether), but that's a ways out.

I don't think, however, that the developer-facing behavior would actually be tri-state. Sites that don't send the header would see the same behavior as those that send `Origin-Agent-Cluster: ?1` from the perspective of API availability (e.g. `document.domain` would be a no-op in both cases), and the OAC header is specified to leave the process model the header supports up to the user agent.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/564#issuecomment-921713395