Post

Wild how far you can push "customizable select" with just #CSS nerdy.dev/nice-select

@naton.mastodon.social.ap.brid.gy

@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()

Anton Andreasson Gistedt

@naton.mastodon.social.ap.brid.gy

3 Feb

@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.

Adam Argyle

@nerdy.dev

3 Feb

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

Luke

@lukewarlow.dev

17 Feb

I thought it was optgroup + legend? codepen.io/editor/lukew... - this seems to work?

codepen.ioUntitledA code demo by Luke Warlow created on CodePen

Adam Argyle

@nerdy.dev

17 Feb

If this is the way I can update my examples 👍 Curious though, what changes after this adjustment?

Luke

@lukewarlow.dev

So if you set the label attribute on optgroup and give it the legend, then in older browsers it will fallback more gracefully (using the label attribute). Because optgroup would be preserved, fieldset wouldn't be. optgroup is also semantically more correct.

17/2/26, 2:57 pm0 reposts0 likes

Adam Argyle

@nerdy.dev

17 Feb

Fallback is great. It’s semantic for a legend to float not in a fieldset?

Luke

@lukewarlow.dev

17 Feb

Yeah so legend is allowed inside optgroup (as well as fieldset) now, it's part of the new content model for select. In older browsers the parser will strip it so it's fine there too.