Post

This is really nice! Where do you get your icons, if you don’t mind my asking?

Sooo cool. I'm very excited for all this to come to multi select boxes so we can make nice tag selector inputs natively etc. Any idea if this is coming?

joey is workin on it I believe, both a custom listbox and multiselect

Nice! Joey?

Why <fieldset> rather than <optgroup>, for better fallback rendering?

Btw Adam if you're running into styling issues using optgroup it's almost definitely a bug. We specifically allowed legend as the first child of optgroup so you could do rich content in it.

Also, you can use attr() to pull the content from the optgroup label into the legend (via a custom prop)

@nerdy.dev Looks lovely, I’m doing something similar atm. But I’m stuck with wanting to ”remote closing” the menu via JS also. Is there something similar to showPicker - but inverted - coming, do you know? Like hidePicker()

cc @una.im for advice here! picker() is a popover, curious if it can be targetted and closed as such? and sounds like you're already aware of the new showPicker(), not sure what's up with a hidePicker()

::picker() is technically a popover but there is some interaction weirdness (see github.com/whatwg/html/...), which stretches to closePopover(). One way to programmatically close it would be to open (& close) another auto popover to close it (though this is super hacky & we need a better solution)

@nerdy.dev Another thing: I notice you use `fieldset` instead of `optgroup`, is that because styleability? I have had a hard time styling my optgroups.. but kept them becuase semantics, I guess.

fieldset/legend is the approved semantic way to create an optgroup that you can style 👍🏻

working on implementing a version of this in our design system as we speak! looks really cool! now let’s do date pickers and combo boxes :)