-
Notifications
You must be signed in to change notification settings - Fork 132
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
[Discussion] New chance for <dialog>? #330
Comments
Hello and thank you for asking! 👋 Things look promising and hopefully we’ll reach a stage where the And there are still reasons to use a11y-dialog (or a similar library):
For what it’s worth, the very next paragraph after the one you’ve quoted states:
So we’re not quite there yet, and we might never be. That being said, once things are clean and shiny all around, I’ll happily update the a11y-dialog documentation to explain when it’s worth using over the native |
Sidenote: The good news for such libraries is that the |
Thank you, @KittyGiraudel, for the long and detailed answer. Which makes very clear that I should have explained the reason for opening the ticket. I am sorry for being so terse. I do believe that we have a need for JavaScript to handle dialogs now and proably for a very long time. I didn't mean to say that Mr. O'Hara's article pointed out various shortcomings of Google's polyfill. Sadly there is no further development for this package so everyone has to work around the deficiences. OTOH you have dropped support for Note to @chalkygames123: We must hope that Chrome and Firefox take this as a cue to finish their support for |
I think that’s fair. I should look at it again. |
Will be added to the documentation in v8. |
Scott O'Hara writes:
The text was updated successfully, but these errors were encountered: