Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web platform integration #8

Open
bakkot opened this issue Feb 19, 2025 · 1 comment
Open

web platform integration #8

bakkot opened this issue Feb 19, 2025 · 1 comment

Comments

@bakkot
Copy link

bakkot commented Feb 19, 2025

DOMExceptions are defined in WebIDL, including this sentence:

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.

Also, structured clone handwaves cloning the .stack as follows:

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.

@ljharb
Copy link
Member

ljharb commented Feb 19, 2025

Thanks for filing this; I'll ensure this is covered in the pre-stage-2.7 PR.

@ljharb ljharb mentioned this issue Feb 19, 2025
30 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants