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 API] Add structured cloning of error types #18208
Comments
Will this edit the |
I suspect don't document clonability of JS because we've never thought about it. IMO a developer would find this useful to know when looking at the error classes. My intent was to add a note like this one for the errors (from DOMException): If there is a good reason not to update the pages (or you are strongly against this) I don't feel strongly since we'll still have the serializability info in the BCD: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RangeError#browser_compatibility |
I'd be happy to document it in JS references—one or two sentences is good enough. |
Status:
This done bar reviews |
Acceptance Criteria
For folks helping with Firefox related documentation
dev-doc-complete
or
Features to document
Related Gecko bugs
https://bugzilla.mozilla.org/show_bug.cgi?id=1556604
Other
Clarifying the scope of this in https://bugzilla.mozilla.org/show_bug.cgi?id=1556604#c32
Essentially though I think it is a BCD update for all the error types to indicate support for serializable errors and also addition to the list of structured clone types.
The open question is mostly around what is not serialized and any limitations of this.
The text was updated successfully, but these errors were encountered: