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.

Sign up for GitHub

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

Jump to bottom

DOMError #17

Open
zloirock opened this issue Dec 3, 2024 · 1 comment
Open

DOMError #17

zloirock opened this issue Dec 3, 2024 · 1 comment

Comments

@zloirock
Copy link

zloirock commented Dec 3, 2024

This proposal does not say anything about DOMError, however, your polyfill returns true for it. Unlike DOMException, it's not a Error subclass. So, should Error.isError(new DOMError(1)) be true?
@ljharb
Copy link
Member

ljharb commented Dec 3, 2024

I was under the impression that it's not possible to actually produce a DOMError in modern browsers (short of manually constructing it), and that it's deprecated in webidl. Safari and Firefox don't seem to implement it at all, altho i see Chrome does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ljharb @zloirock