<dd>

<p>Some parts of the language described by this specification only support JavaScript as the

type</span> used to refer to JavaScript in this specification is <code

data-x="">text/javascript</code>, since that is the most commonly used type, <span

data-x="willful violation">despite it being an officially obsoleted type</span> according to RFC

4329. <ref spec=RFC4329></p>

<p>The following terms are defined in the JavaScript specification and used in this specification:</p>

<ul class="brief">

<h3>Safe passing of structured data</h3>

<p>This section uses the terminology and typographic conventions from the JavaScript

<h4><dfn>Cloneable objects</dfn></h4>

<var>placeholderResult</var>, now holds a reference to <var>transferResult</var>.</p>

<p class="note">This is a rather unusual low-level operation for which no primitives are

</li>

<li><p>Add <var>transferResult</var> as the last element of

<p>The following JavaScript function shows how the tree walk could be implemented. The <var>root</var> argument is the root of the tree to walk (either a <span>sectioning

content</span> element or a <span>sectioning root</span> element), and the <var>enter</var> and <var>exit</var> arguments are callbacks that are called with

<pre>function (root, enter, exit) {

var node = root;

with only the "<code data-x="">u</code>" flag specified, compiles successfully, then the resulting regular expression is the element's

<dfn>compiled pattern regular expression</dfn>. If the element has no such attribute, or if the

value doesn't compile successfully, then the element has no <span>compiled pattern regular

<p class="note">If the value doesn't compile successfully, user agents are encouraged to log this

fact in a developer console, to aid debugging.</p>

with the requirements of the JavaScript specification's <i data-x="js-prod-Script">Script</i> or

<i data-x="js-prod-Module">Module</i> productions, for <span data-x="classic script">classic

scripts</span> and <span data-x="module script">module scripts</span> respectively. <ref

<p>When used to include <span data-x="data block">data blocks</span>, the data must be embedded

inline, the format of the data must be given using the <code

<h5 id="scriptingLanguages">Scripting languages</h5>

<p>A <dfn>JavaScript MIME type</dfn> is a <span>MIME type</span> string that is one of the

<ul class="brief">

<li><code>application/ecmascript</code>

data-x="js-ScriptEvaluation">ScriptEvaluation</span> or <span

data-x="js-ModuleEvaluation">ModuleEvaluation</span> to cease immediately, emptying the

<span>JavaScript execution context stack</span> without triggering any of the normal mechanisms

<p>User agents may impose resource limitations on scripts, for example CPU quotas, memory limits,

total execution time limits, or bandwidth limitations. When a script exceeds a limit, the user

specify certain invariants about how promise operations execute with a clean <span>JavaScript

execution context stack</span> and in a certain order. However, as of the time of this writing

the definition of <span data-x="js-EnqueueJob">EnqueueJob</span> in that specification is not

<p class="note">This is not strictly true. It is in fact possible, by taking liberal advantage of

the many "implementation defined" sections of the algorithm, to contort it to our purposes.

of their processing model. This specification defines the rest of their processing model: how the

module system is bootstrapped, via the <code>script</code> element with <code

data-x="attr-script-type">type</code> attribute set to "<code data-x="">module</code>", and how

<p class="note">Although the JavaScript specification speaks in terms of "scripts" versus

"modules", in general this specification speaks in terms of <span data-x="classic script">classic

<p>JavaScript contains an implementation-defined <span

data-x="js-HostResolveImportedModule">HostResolveImportedModule</span> abstract operation. User

<ol>

<li><p>Let <var>referencing module script</var> be

<p>JavaScript contains an implementation-defined <span

data-x="js-HostPromiseRejectionTracker">HostPromiseRejectionTracker</span>(<var>promise</var>,

<var>operation</var>) abstract operation. User agents must use the following implementation:

<ol>

legacy content: one that uses the presence of <code data-x="dom-document-all">document.all</code>

as a way to detect legacy user agents, and one that only supports those legacy user agents and

uses the <code data-x="dom-document-all">document.all</code> object without testing for its

<hr>

<dt id="refsE163">[E163]</dt>

<dd><cite>Recommendation E.163 &mdash; Numbering Plan for The International Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November 1988.</dd>

<dt id="refsEDITING">[EDITING]</dt>

<dd><cite><a href="https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html">HTML Editing APIs</a></cite>, A. Gregor. W3C Editing APIs CG.</dd>

<dt id="refsISO8601">[ISO8601]</dt>

<dd>(Non-normative) <cite><a href="http://isotc.iso.org/livelink/livelink/4021199/ISO_8601_2004_E.zip?func=doc.Fetch&amp;nodeid=4021199">ISO8601: Data elements and interchange formats &mdash; Information interchange &mdash; Representation of dates and times</a></cite>. ISO.</dd>

<dt id="refsJLREQ">[JLREQ]</dt>

<dd><cite><a href="https://www.w3.org/TR/jlreq/">Requirements for Japanese Text Layout</a></cite>. W3C.</dd> <!-- too many editors to list -->