[ativzzz]

Was this worth developing?

We already have infinite popover js/css libraries so this doesn't solve any unsolved problem. I suspect this will be like select, where you almost always want some functionality or styling that can't be done natively so you reach for a custom solution or use some existing library.

Maybe if I start a new app this is OK as a stopgap until I need more functionality (which always happens), but in my existing app I'm just using the already existing popover library for consistency

[dmix]

Every single app having to import the same popper library, for over a decade, indicates there's sufficient need for native support.

I've also been a proponent of a combobox becoming native (for ex: a select box of Countries where you can filter by typing) https://www.w3.org/WAI/ARIA/apg/patterns/combobox/#:~:text=C.... and ideally multi-select for ex a tag selector.

[cynicalsecurity]

That's the point. Why make the life easier for websites that display pop-ups. Pop-ups are pure evil.

[filleduchaos]

What does that have to do with popovers, though?

[woodrowbarlow]

for anyone who views third-party dependencies as a liability (license changes, leftpad drama, etc.), the ability to easily ditch them in favor of native implementations is a win.

[The_Colonel]

Yeah, just like e. g. flexbox doesn't solve any unsolved problems, you can do any layout with JavaScript.

The problem with dropdown is that it has an immense variety of use cases which is difficult to generify. Still, I'm happy we have a basic native Select element, it's competely fine for 8/10 use cases, and okish for 1/10.

OTOH, I believe that a popover is a much more generic feature and most you'd like to customize is styling.