>
> On 12/14/21 11:35 AM, Daniel Bratell wrote:
>
> It seems more or less everyone agrees on this being a good thing, so it
> mainly comes down to web compatibility.
>
> How much of the web will break, and how badly. The numbers mentioned, 0.5%
> of sites set document.domain, 0.05% seem to depend on document.domain, are
> quite high. One thing I didn't quite pick up is what happens if you try to
> set document.domain when it's not settable. Will it silently pretend to
> work, or will that also be a possible break point?
>
>
It does nothing, silently. This matches the behaviour when
Origin-Agent-Cluster is explicitly set to true. From a developer's
perspective, the current default matches explicit-false and the future
default is meant to match explicit-true.

Reference: Step 7 of "The domain setter steps are" of
https://html.spec.whatwg.org/multipage/origin.html#dom-document-domain.

There is also the question of reverse origin trial and enterprise flags. If
> Origin-Agent-Cluster can be set with <meta http-equiv="....">, then I don't
> see any use for an origin trial since that would be activated the same way.
> An enterprise flag might still be needed though, since that covers
> installations where the client can be configured, but applications can not
> be changed.
>
>
An enterprise policy has been implemented
<https://chromiumdash.appspot.com/commit/b9ad777ae21db7dbf1248e35f438d9afed62a108>
.
We didn't think a reverse origin trial would make sense, since any site can
already opt-out by setting the Origin-Agent-Cluster header.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALG6KPOae7vcJmfZBJUZFMbLk7qrcxa0ot%2BLnTJF25rqHp2_kg%40mail.gmail.com.

Reply via email to