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
Web IDL enumerates the ES Error object constructor names that are usable in Web IDL for simple exceptions, but the text that follows the list also enumerates those which aren’t:
These correspond to all of the ECMAScript error objects (apart from SyntaxError and Error, which are deliberately omitted as they are reserved for use by the ECMAScript parser and by authors, respectively).
This list is no longer complete because of AggregateError. Options include:
Adding AggregateError to the explicit exclusions list, and future additions as well, as they are introduced
Restructuring the sentence so that it doesn’t claim to be exhaustive
Changing the references to “Error object” to “NativeError object”, in which case the only excluded item would be “SyntaxError”. (The odds of new NativeError objects being introduced seems lower than that of new Error objects being introduced.)
(Spun off from exception-related PR feedback because this was a pre-existing issue in the text.)
The text was updated successfully, but these errors were encountered:
I think we actually want to allow specs to create AggregateErrors. E.g. whatwg/streams#1134 . We probably need to add special wrappers for that though...
Web IDL enumerates the ES Error object constructor names that are usable in Web IDL for simple exceptions, but the text that follows the list also enumerates those which aren’t:
This list is no longer complete because of AggregateError. Options include:
(Spun off from exception-related PR feedback because this was a pre-existing issue in the text.)
The text was updated successfully, but these errors were encountered: