Frontend

Edge cases to consider when choosing or building bespoke UI components:

• keyboard navigation + Esc key behavior
• headless/overridable styles
• i18n
• screen reader support
• date pickers
• nested modals
• sorting/filtering/multiselect in comboboxes/data grids

What else?

Edge cases to consider when choosing or building bespoke UI components:

• keyboard navigation + Esc key behavior
• headless/overridable styles
• i18n
• screen reader support
• date pickers
• nested modals
• sorting/filtering/multiselect in comboboxes/data grids

What else?

https://youtu.be/9-6deom3ZdY

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

Mostly Typescript/Python, lead dev at @atomichub. On side working on Ondly - web3 career space.
Love everything sci fi related.
https://github.com/DamianBusz

Yeah it’s cool if you have all that a11 controls but technically I believe it you would have focus on the element and press escape most modern libraries would handle that case and close the dropdown/modal. I might be wrong tho lol

More generally, captured focus areas within captured focus areas, or floating UI within floating UI. Like a dropdown menu inside of a modal.

If done right, they should create a "hierarchy" of escape key presses.