You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, if an implementation gives native Error objects special powers or nonstandard properties (such as a stack property), it should also expose those on DOMException objects.
Presumably this would need to be reworded. Engines are not currently consistent about this; in Chrome it apparently depends on how it's thrown.
User agents should attach a serialized representation of any interesting accompanying data which are not yet specified, notably the stack property, to serialized.
This too would presumably need to be reworded.
Also there would need to be WPT tests for presence of .stack as a string on DOMExceptions, both manually created and thrown, as well as for cloning of stacks with structured clone.
The text was updated successfully, but these errors were encountered:
DOMExceptions are defined in WebIDL, including this sentence:
Presumably this would need to be reworded. Engines are not currently consistent about this; in Chrome it apparently depends on how it's thrown.
Also, structured clone handwaves cloning the
.stack
as follows:This too would presumably need to be reworded.
Also there would need to be WPT tests for presence of
.stack
as a string on DOMExceptions, both manually created and thrown, as well as for cloning of stacks with structured clone.The text was updated successfully, but these errors were encountered: