From 41a2b501aaaba712b50a71dd6b268085cb201980 Mon Sep 17 00:00:00 2001 From: Shu-yu Guo Date: Wed, 31 May 2023 00:13:40 -0700 Subject: [PATCH] Editorial: formalize the concept of a realm's agent Follows https://github.com/tc39/ecma262/pull/3058. See https://github.com/tc39/ecma262/issues/1357 for more background. --- source | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/source b/source index 9adf244607b..328fbab5a43 100644 --- a/source +++ b/source @@ -96995,11 +96995,14 @@ new PaymentRequest(…); // Allowed to use

  • Return agent.

    • +

    For a realm realm, the agent whose [[Signifier]] is + realm.[[AgentSignifier]] is the realm's agent.

    +

    The relevant agent for a platform object platformObject is platformObject's relevant realm's agent. This pointer is not yet defined in the JavaScript specification; see tc39/ecma262#1357.

    + data-x="concept-relevant-realm">relevant realm's agent.

    The agent equivalent of the current realm is the surrounding agent.

    @@ -97147,7 +97150,7 @@ new PaymentRequest(…); // Allowed to use

  • Assert: outside settings is not null.

  • Let ownerAgent be outside settings's realm's agent.

    • + settings object's realm">realm's agent.

  • Set agentCluster to the agent cluster which contains ownerAgent.

    • @@ -97450,10 +97453,6 @@ new PaymentRequest(…); // Allowed to use

  • Let realm be realm execution context's Realm component.

    • -

  • Set realm's agent to agent. This pointer - is not yet defined in the JavaScript specification; see tc39/ecma262#1357.

    • -

  • If agent's agent cluster's cross-origin isolation mode is "