@@ -13392,7 +13392,8 @@ fragment:
13392
13392
<pre class="idl">
13393
13393
[
13394
13394
Exposed=(Window,Worker),
13395
- Constructor(optional DOMString message = "", optional DOMString name = "Error")
13395
+ Constructor(optional DOMString message = "", optional DOMString name = "Error"),
13396
+ Serializable
13396
13397
]
13397
13398
interface DOMException { // but see below note about ECMAScript binding
13398
13399
readonly attribute DOMString name;
@@ -13449,6 +13450,26 @@ The <dfn attribute for="DOMException"><code>code</code></dfn> attribute's getter
13449
13450
legacy code indicated in the [=error names table=] for this {{DOMException}} object's
13450
13451
[=DOMException/name=], or 0 if no such entry exists in the table.
13451
13452
13453
+ {{DOMException}} objects are [=serializable objects=].
13454
+
13455
+ Their [=serialization steps=], given <var>value</var> and <var>serialized</var>, are:
13456
+
13457
+ <ol>
13458
+ <li>Set <var>serialized</var>.\[[Name]] to <var>value</var>'s [=DOMException/name=].</li>
13459
+ <li>Set <var>serialized</var>.\[[Message]] to <var>value</var>'s [=DOMException/message=].</li>
13460
+ <li>User agents should attach a serialized representation of any interesting accompanying data
13461
+ which are not yet specified, notably the <code>stack</code> property, to
13462
+ <var>serialized</var>.</li>
13463
+ </ol>
13464
+
13465
+ Their [=deserialization steps=], given <var>value</var> and <var>serialized</var>, are:
13466
+
13467
+ <ol>
13468
+ <li><Set <var>value</var>'s [=DOMException/name=] to <var>serialized</var>.\[[Name]].</li>
13469
+ <li><Set <var>value</var>'s [=DOMException/message=] to <var>serialized</var>.\[[Message]].</li>
13470
+ <li>If any other data is attached to <var>serialized</var>, then deserialize and attach it to
13471
+ <var>value</var>.</li>
13472
+ </ol>
13452
13473
13453
13474
<h3 id="DOMTimeStamp" typedef oldids="common-DOMTimeStamp">DOMTimeStamp</h3>
13454
13475
0 commit comments