4 ms·
I even remember I made a tweet for fun https://twitter.com/vponamariov/status/1528758532182515714 https://twitter.com/vponamariov/status/1528758532182515714 wh
by Akcium 4y ago
I even remember I made a tweet for fun https://twitter.com/vponamariov/status/1528758532182515714 https://twitter.com/vponamariov/status/1528758532182515714
when I started working on a project that had up to 3(!!) modals inside.
It's not only hard for users, it's hard for developers, when they have scroll issues, when they should update each other, when you should keep track of URL (what if user hits F5 or wants to share these...modal hell)
- chomp 4y agoI personally also find it hard getting accessibility to work right. Depending on the modal and js library used to generate it, getting aria tags to work right always feels difficult.
- clairity 4y agothe new-ish <dialog> tag with a <form method="dialog"><button>Close</button></form> inside, combined with styling the pseudo-element ::backdrop, comes very close to being javascript-less built-in solution for modals. you still need js to trigger opening the dialog though, but that can be as simple as document.querySelector('#dialog').showModal() apparently <dialog>'s still needs some accessibility/interaction improvements to be a first-class solution, but it's getting there: https://nolanlawson.com/2022/06/14/dialogs-and-shadow-dom-can-we-make-it-accessible/ https://nolanlawson.com/2022/06/14/dialogs-and-shadow-dom-ca...