Add atob, btoa, structuredClone to shadow realms

Author: Ms2ger

source

@@ -10659,7 +10659,7 @@ o.myself = o;</code></pre>
 
   <div w-nodev>
 
-  <p>The <dfn method for="WindowOrWorkerGlobalScope"
+  <p>The <dfn method for="WindowOrWorkerOrShadowRealmGlobalScope"
   data-x="dom-structuredClone"><code>structuredClone(<var>value</var>,
   <var>options</var>)</code></dfn> method steps are:</p>
 
@@ -112750,6 +112750,87 @@ interface mixin <dfn interface>WindowEventHandlers</dfn> {
   </div>
 
 
+  <h3 id="windoworworkerorshadowrealmglobalscope-mixin">The <code>WindowOrWorkerOrShadowRealmGlobalScope</code> mixin</h3>
+
+  <p>The <code>WindowOrWorkerOrShadowRealmGlobalScope</code> mixin is for use of APIs that are to be exposed on
+    <code>Window</code> and <code>WorkerGlobalScope</code> objects.</p>
+
+    <p class="note">Other standards are encouraged to further extend it using <code data-x="">partial
+    interface mixin <span>WindowOrWorkerOrShadowRealmGlobalScope</span> { &hellip; };</code> along with an
+    appropriate reference.</p>
+
+    <pre><code class="idl">interface mixin <dfn interface>WindowOrWorkerOrShadowRealmGlobalScope</dfn> {
+    // base64 utility methods
+    DOMString <span data-x="dom-btoa">btoa</span>(DOMString data);
+    ByteString <span data-x="dom-atob">atob</span>(DOMString data);
+
+    // structured cloning
+    any <span data-x="dom-structuredClone">structuredClone</span>(any value, optional <span>StructuredSerializeOptions</span> options = {});
+  };
+  <span>Window</span> includes <span>WindowOrWorkerGlobalScope</span>;
+  <span>WorkerGlobalScope</span> includes <span>WindowOrWorkerGlobalScope</span>;
+  <span>ShadowRealmGlobalScope</span> includes <span>WindowOrWorkerGlobalScope</span>;</code></pre>
+
+  <h4 id="atob">Base64 utility methods</h4>
+
+  <p>The <code data-x="dom-atob">atob()</code> and <code data-x="dom-btoa">btoa()</code> methods
+  allow developers to transform content to and from the base64 encoding.</p>
+
+  <p class="note">In these APIs, for mnemonic purposes, the "b" can be considered to stand for
+  "binary", and the "a" for "ASCII". In practice, though, for primarily historical reasons, both the
+  input and output of these functions are Unicode strings.</p>
+
+  <dl class="domintro">
+    <dt><code data-x=""><var>result</var> = self.<span subdfn data-x="dom-btoa">btoa</span>(<var>data</var>)</code></dt>
+
+    <dd>
+    <p>Takes the input data, in the form of a Unicode string containing only characters in the range
+    U+0000 to U+00FF, each representing a binary byte with values 0x00 to 0xFF respectively, and
+    converts it to its base64 representation, which it returns.</p>
+
+    <p>Throws an <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code>
+    exception if the input string contains any out-of-range characters.</p>
+    </dd>
+
+    <dt><code data-x=""><var>result</var> = self.<span subdfn data-x="dom-atob">atob</span>(<var>data</var>)</code></dt>
+
+    <dd>
+    <p>Takes the input data, in the form of a Unicode string containing base64-encoded binary data,
+    decodes it, and returns a string consisting of characters in the range U+0000 to U+00FF, each
+    representing a binary byte with values 0x00 to 0xFF respectively, corresponding to that binary
+    data.</p>
+
+    <p>Throws an <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code> if the
+    input string is not valid base64 data.</p>
+    </dd>
+  </dl>
+
+  <div w-nodev>
+
+  <p>The <dfn method for="WindowOrWorkerOrShadowRealmGlobalScope" data-x="dom-btoa"><code
+  id="dom-windowbase64-btoa">btoa(<var>data</var>)</code></dfn> method must throw an
+  <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code> if <var>data</var>
+  contains any character whose code point is greater than U+00FF. Otherwise, the user agent must
+  convert <var>data</var> to a byte sequence whose <var>n</var>th byte is the eight-bit
+  representation of the <var>n</var>th code point of <var>data</var>, and then must apply
+  <span>forgiving-base64 encode</span> to that byte sequence and return the result.</p>
+
+  <p>The <dfn method for="WindowOrWorkerOrShadowRealmGlobalScope" data-x="dom-atob"><code
+  id="dom-windowbase64-atob">atob(<var>data</var>)</code></dfn> method steps are:</p>
+
+  <ol>
+    <li><p>Let <var>decodedData</var> be the result of running <span>forgiving-base64 decode</span>
+    on <var>data</var>.</p></li>
+
+    <li><p>If <var>decodedData</var> is failure, then throw an
+    <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code>.</p></li>
+
+    <li><p>Return <var>decodedData</var>.</p></li>
+  </ol>
+
+  </div>
+
+
   <h3 id="windoworworkerglobalscope-mixin">The <code>WindowOrWorkerGlobalScope</code> mixin</h3>
 
   <p>The <code>WindowOrWorkerGlobalScope</code> mixin is for use of APIs that are to be exposed on
@@ -112768,10 +112849,6 @@ interface mixin <dfn interface>WindowOrWorkerGlobalScope</dfn> {
 
   undefined <span data-x="dom-reportError">reportError</span>(any e);
 
-  // base64 utility methods
-  DOMString <span data-x="dom-btoa">btoa</span>(DOMString data);
-  ByteString <span data-x="dom-atob">atob</span>(DOMString data);
-
   // timers
   long <span data-x="dom-setTimeout">setTimeout</span>(<span>TimerHandler</span> handler, optional long timeout = 0, any... arguments);
   undefined <span data-x="dom-clearTimeout">clearTimeout</span>(optional long id = 0);
@@ -112784,9 +112861,6 @@ interface mixin <dfn interface>WindowOrWorkerGlobalScope</dfn> {
   // ImageBitmap
   <span data-x="idl-Promise">Promise</span>&lt;<span>ImageBitmap</span>&gt; <span data-x="dom-createImageBitmap">createImageBitmap</span>(<span>ImageBitmapSource</span> image, optional <span>ImageBitmapOptions</span> options = {});
   <span data-x="idl-Promise">Promise</span>&lt;<span>ImageBitmap</span>&gt; <span data-x="dom-createImageBitmap">createImageBitmap</span>(<span>ImageBitmapSource</span> image, long sx, long sy, long sw, long sh, optional <span>ImageBitmapOptions</span> options = {});
-
-  // structured cloning
-  any <span data-x="dom-structuredClone">structuredClone</span>(any value, optional <span>StructuredSerializeOptions</span> options = {});
 };
 <span>Window</span> includes <span>WindowOrWorkerGlobalScope</span>;
 <span>WorkerGlobalScope</span> includes <span>WindowOrWorkerGlobalScope</span>;</code></pre>
@@ -112845,66 +112919,6 @@ document.body.appendChild(frame)</code></pre>
   </div>
 
 
-  <h3 id="atob">Base64 utility methods</h3>
-
-  <p>The <code data-x="dom-atob">atob()</code> and <code data-x="dom-btoa">btoa()</code> methods
-  allow developers to transform content to and from the base64 encoding.</p>
-
-  <p class="note">In these APIs, for mnemonic purposes, the "b" can be considered to stand for
-  "binary", and the "a" for "ASCII". In practice, though, for primarily historical reasons, both the
-  input and output of these functions are Unicode strings.</p>
-
-  <dl class="domintro">
-   <dt><code data-x=""><var>result</var> = self.<span subdfn data-x="dom-btoa">btoa</span>(<var>data</var>)</code></dt>
-
-   <dd>
-    <p>Takes the input data, in the form of a Unicode string containing only characters in the range
-    U+0000 to U+00FF, each representing a binary byte with values 0x00 to 0xFF respectively, and
-    converts it to its base64 representation, which it returns.</p>
-
-    <p>Throws an <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code>
-    exception if the input string contains any out-of-range characters.</p>
-   </dd>
-
-   <dt><code data-x=""><var>result</var> = self.<span subdfn data-x="dom-atob">atob</span>(<var>data</var>)</code></dt>
-
-   <dd>
-    <p>Takes the input data, in the form of a Unicode string containing base64-encoded binary data,
-    decodes it, and returns a string consisting of characters in the range U+0000 to U+00FF, each
-    representing a binary byte with values 0x00 to 0xFF respectively, corresponding to that binary
-    data.</p>
-
-    <p>Throws an <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code> if the
-    input string is not valid base64 data.</p>
-   </dd>
-  </dl>
-
-  <div w-nodev>
-
-  <p>The <dfn method for="WindowOrWorkerGlobalScope" data-x="dom-btoa"><code
-  id="dom-windowbase64-btoa">btoa(<var>data</var>)</code></dfn> method must throw an
-  <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code> if <var>data</var>
-  contains any character whose code point is greater than U+00FF. Otherwise, the user agent must
-  convert <var>data</var> to a byte sequence whose <var>n</var>th byte is the eight-bit
-  representation of the <var>n</var>th code point of <var>data</var>, and then must apply
-  <span>forgiving-base64 encode</span> to that byte sequence and return the result.</p>
-
-  <p>The <dfn method for="WindowOrWorkerGlobalScope" data-x="dom-atob"><code
-  id="dom-windowbase64-atob">atob(<var>data</var>)</code></dfn> method steps are:</p>
-
-  <ol>
-   <li><p>Let <var>decodedData</var> be the result of running <span>forgiving-base64 decode</span>
-   on <var>data</var>.</p></li>
-
-   <li><p>If <var>decodedData</var> is failure, then throw an
-   <span>"<code>InvalidCharacterError</code>"</span> <code>DOMException</code>.</p></li>
-
-   <li><p>Return <var>decodedData</var>.</p></li>
-  </ol>
-
-  </div>
-
-
   <h3 split-filename="dynamic-markup-insertion"><dfn>Dynamic markup insertion</dfn></h3>
 
   <p class="note">APIs for dynamically inserting markup into the document interact with the parser,