-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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
Missing Dialog element #16880
Comments
Generally TypeScript does not include the experimental technologies that aren't widely adopted tend not to be added to TypeScript. This helps developers to not accidentally create code that is broken on most browsers. Developers who know they are only going to be running on Chrome, can of course add these types to their environment themselves. |
Dialog is a Living Standard and the readme for TSJS-lib-generator says: |
No. TypeScript does not cover everything in the standard until it is widely adopted. |
Is that recorded somewhere? The only thing I've found is the readme saying "Living Standard" is the baseline. |
The process of including a definition on DT in the default library is painful. it involves errors to all users of the DT definition file, and a cascade of issues in depending packages. |
@jhpratt I'm a beginner so I could be wrong but I think your two options are waiting for Typescript 2.6 or writing your own definition in the short term https://www.typescriptlang.org/docs/handbook/declaration-files/introduction.html |
@terrylewis60 What's your problem? This is absolutely unacceptable behavior period, let alone in the open source community. @arjunyel Thanks! I'll check that out. |
I think someone doesn't understand being subscribed to a thread via e-mail in GitHub and thinks we are intentionally sending them e-mails. Someone needs to learn how to use a computer. @jhpratt as mentioned, an interface file with something that introduced what you are looking for. The state of this issue though now indicates that the typings are now in |
TypeScript Version: 2.4.1
Code
Expected behavior:
Understand what a dialog element is
Actual behavior:
[ts] Cannot find name 'HTMLDialogElement'.
The text was updated successfully, but these errors were encountered: