Size Change: +102 B (+0.01%)

Total Size: 1.83 MB

_{compressed-size-action}

Can be useful if you have a lot. But now you have to search in order to see anything at all, even if you just have a few attributes. Is there a way to show at least, say, 8 items always? It's likely not going to be the majority of sites having such few attributes, if they use them at all.

Can be useful if you have a lot. But now you have to search in order to see anything at all, even if you just have a few attributes. Is there a way to show at least, say, 8 items always? It's likely not going to be the majority of sites having such few attributes, if they use them at all.

I think that's a combobox limitation, you need at least to click on the search bar. Ping @WordPress/gutenberg-components so they can answer better.

I can add a searchcontrol on the top of the list and filter manually, but getting all of that together inside a dropdown component is tricky.

Can be useful if you have a lot. But now you have to search in order to see anything at all, even if you just have a few attributes. Is there a way to show at least, say, 8 items always? It's likely not going to be the majority of sites having such few attributes, if they use them at all.

I think that's a combobox limitation, you need at least to click on the search bar. Ping @WordPress/gutenberg-components so they can answer better.

I can add a searchcontrol on the top of the list and filter manually, but getting all of that together inside a dropdown component is tricky.

I think you might want to set expandOnFocus to true, in order to reveal items when focused; and you might want to focus the combobox once it's opened. That should ensure results are displayed immediately.

In terms of how many items to display, with the current item height there will be ~2-2.5 results displayed, so you might want to override the .components-form-token-field__suggestions-list's max-height and provide a bigger number in order to be able to accommodate more items. We usually don't recommend style overrides, but the ComboboxControl API is a bit limited right now.

I added the height to be able to display more items.
I'm not 100% convinced about forcing autofocus on the editor on the tool item click though.

I'm not 100% convinced about forcing autofocus on the editor on the tool item click though.

I understand the uncertainty there and I don't have strong feelings either way; my suggestion was mostly to address @jasmussen's concerns:

But now you have to search in order to see anything at all, even if you just have a few attributes. Is there a way to show at least, say, 8 items always?

The main thing is striking the right balance. Forcing you to search if you have only two or three bindings may be too much, since that could be the 80% use case.

The main thing is striking the right balance. Forcing you to search if you have only two or three bindings may be too much, since that could be the 80% use case.

If 80% of the time we'll have two or three bindings, then we might as well not use a combobox but just a regular select/dropdown field?

To be fair, that's a question from my end! So far I've only used bindings for basic stuff, quote of the day, random image, that sort of thing.

But depending on experience and feedback on these it could simply be a progressive thing, and that's perhaps what you suggest: if there are less than 10 bindings, just show them in the flyout. If there's more than 10, do the combobox.

To be fair, that's a question from my end! So far I've only used bindings for basic stuff, quote of the day, random image, that sort of thing.

But depending on experience and feedback on these it could simply be a progressive thing, and that's perhaps what you suggest: if there are less than 10 bindings, just show them in the flyout. If there's more than 10, do the combobox.

Sounds like a good plan to me 👍 And then the autofocusing wouldn't feel as awkward.

All of these are just experiments to enable this discussions 😅
There is still some feedback from developers with tons of fields wanting a more powerful solution like the dataviews, which I guess it will make field validation easier.

Closed, #71542 will replace it.