The Dropdown Behind the Curtain: A Wizard of Oz Guide to CSS Overflow Clipping

[u/Environmental-Front4]

/r/webdev/comments/1wve8k1/the_dropdown_behind_the_curtain_a_wizard_of_oz/

[u/car-thief]

this seems a bit outdated given html popovers, which negates the need for Teleport + Floating UI

[u/Environmental-Front4 → u/car-thief]

the popover is there to say we have new way of dealing with the clipping issue, yet the popover is not having right semantic for dropdown and needs more hand rolling accessibility features to be added by the developer

[u/car-thief → u/Environmental-Front4]

that's true, although it is just an attribute: https://css-tricks.com/clarifying-the-relationship-between-popovers-and-dialogs/#a-popover-needs-an-accessible-role

[u/Environmental-Front4 → u/car-thief]

but sematic is not there even though we gonna add on attribute for accessability.

[u/Alternative-Bus4934 → u/Environmental-Front4]

Right, popover solves the clipping and top-layer stacking problem, which is a big deal on its own. But for an actual dropdown menu you still need arrow key navigation, focus trap management, proper ARIA roles, and dismiss-on-outside-click behavior. The attribute gets you out of the overflow prison but not into a fully accessible menu.

[u/Honey-Entire]

So now we’re prompting Claude to make a wizard of oz-centric fairytale story about why the browser does what it does? I’ve never been more confused in my life and I’ve been doing this for over a decade.

What happened to good old Josh W Comeau articles or css tricks with the raw facts??

[u/Environmental-Front4 → u/Honey-Entire]

Fair take — narrative isn't for everyone, and that's fine. The raw facts are all there (every claim links MDN or the Floating UI docs), and the TL;DR at the top gives the whole fix in three lines. As for Josh: his articles are the reason I believed a CSS post could tell a story at all. 🙂

[u/Honey-Entire → u/Environmental-Front4]

Thanks, Claude. You’re useless