From a83b58693a6926b7d387cb9e7b4e15f16fa85174 Mon Sep 17 00:00:00 2001 From: Michael Dyck Date: Wed, 31 Aug 2022 23:46:33 -0400 Subject: [PATCH] fixup: "execution context" -> "ExecutionContext Record" in some prose --- spec.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/spec.html b/spec.html index 6e1f0a198b..b0bbef86e9 100644 --- a/spec.html +++ b/spec.html @@ -11902,7 +11902,7 @@

Execution Contexts

a Module Record, a Script Record, or *null* - The Module Record or Script Record from which associated code originates. If there is no originating script or module, as is the case for the original execution context created in InitializeHostDefinedRealm, the value is *null*. + The Module Record or Script Record from which associated code originates. If there is no originating script or module, as is the case for the original ExecutionContext Record created in InitializeHostDefinedRealm, the value is *null*. @@ -12112,18 +12112,18 @@

Jobs and Host Operations to Enqueue Jobs

At any particular time, _scriptOrModule_ (a Script Record, a Module Record, or *null*) is the active script or module if all of the following conditions are true:

At any particular time, an execution is prepared to evaluate ECMAScript code if all of the following conditions are true:

-

Host environments may prepare an execution to evaluate code by pushing execution contexts onto the execution context stack. The specific steps are implementation-defined.

-

The specific choice of Realm is up to the host environment. This initial execution context and Realm is only in use before any callback function is invoked. When a callback function related to a Job, like a Promise handler, is invoked, the invocation pushes its own execution context and Realm.

+

Host environments may prepare an execution to evaluate code by pushing ExecutionContext Records onto the execution context stack. The specific steps are implementation-defined.

+

The specific choice of Realm is up to the host environment. This initial ExecutionContext Record and Realm is only in use before any callback function is invoked. When a callback function related to a Job, like a Promise handler, is invoked, the invocation pushes its own ExecutionContext Record and Realm.

Particular kinds of Jobs have additional conformance requirements.