Lena Morita

> Speaking of... the inline label option causes the select to fill the container, is that fixable? @jameskoster This shouldn't be the case 🤔 It should hug the current option...

> Yup, here's a demo: Ah ok, good catch. I fixed it in `labelPosition="edge"` (fbcbbaeff4d3355190c33e5d8d6c93287a19d051), but I'd say the behavior is correct in `labelPosition="side"`. I also noticed that `labelPosition="edge"` cannot...

> That appears to use the full-size `chevronDown` icon. It should use the `chevronDownSmall` unscaled, no? Ok, I'll make a note to follow up on this 👍

Does anyone have any blockers to merging this? FWIW it's as early as we can be in the 6.7 release cycle so we'll have a good amount of time to...

> > There is a CSS [field-sizing property](https://developer.mozilla.org/en-US/docs/Web/CSS/field-sizing#result_2) in the pipeline that does exactly what we want, and it's shipping in Chrome but we're still waiting on Safari and Firefox....

Removing the Needs Dev Note label because we don't necessarily want to advertise this variant when it's still quite niche in Gutenberg itself.

Hmm, good one. Can you post an issue so we can keep track of it? Also, does it still occur if the longest option value is not `disabled`? I'm wondering...

I was able to confirm that this only happens when the option is longer than the currently selected value. Nothing to do with `disabled` attributes. Probably hasn't manifested because the...

@ciampo I accidentally confounded the two at first too, but this issue is for a `disabled` state on the _entire component_, not the individual options. This was the use case...

It's very confusing, but this issue is for supporting `disabled` of the _entire_ component. #63612 is for keeping _items_ accessible when individual _items_ are disabled (item-level disabling is already supported)....