Question about DOMException constructor behavior testing #27151
Closed
Labels
Comments
cc @domenic |
We should test all of them. "Deprecated" means "don't use in future specs", but it's still part of the web platform and should still be tested. |
@domenic Thank you for your advice! So it seems that the current test cases are incomplete on testing these (deprecated) error code mappings. I'll send a PR for it. |
domenic
pushed a commit
that referenced
this issue
Jan 15, 2021
In particular, this tests the deprecated ones, some removed ones, and some newer error names which intentionally don't have legacy error codes. See also heycam/webidl#946. Closes #27151.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the test of the error name table of DOMException in this file, the error codes 2, 6, 16, 17 are omitted. Is this intended?
In the WebIDL, the error codes 1, 2, 6, 15, 16, and 17 are marked "Deprecated". https://heycam.github.io/webidl/#idl-DOMException-error-names
If the above 4 codes are intentionally omitted because of the deprecation, then should we keep testing about the error code 1 and 15?
The text was updated successfully, but these errors were encountered: