ui: make selection fields searchable

ui: make selection fields searchable

[666Goofy666]

Hi,
thanks for your continued work on Proxmox.

I would like to make pools and bridges forms selection fields searchable 

I tried something like this patch : https://lore.proxmox.com/pve-devel/20240412091613.30038-1-f.ebner@proxmox.com/ to `pve-manager/www/manager6/form/PoolSelector.js` and it works as expected.

However, for `pve-manager/www/manager6/form/BridgeSelector.js` the situation is a bit different because the current behavior should be preserved: select the first filtered element

at `pve-manager/www/manager6/qemu/NetworkEdit.js:83` and LXC (implicite true) there is `autoSelect: true` which is handled/overridden at `proxmox-widget-toolkit/src/form/ComboGrid.js:435`
This makes searching impossible, because as soon as one character is typed, the first result is match.

What would be the recommended approach?

Thanks,

Goofy

Re: ui: make selection fields searchable

[Dominik Csapak]

On 7/14/26 1:20 PM, 666Goofy666 wrote:
> Hi,
> thanks for your continued work on Proxmox.
> 
> I would like to make pools and bridges forms selection fields searchable
> 
> I tried something like this patch : https://lore.proxmox.com/pve-devel/20240412091613.30038-1-f.ebner@proxmox.com/ to `pve-manager/www/manager6/form/PoolSelector.js` and it works as expected.
> 
> However, for `pve-manager/www/manager6/form/BridgeSelector.js` the situation is a bit different because the current behavior should be preserved: select the first filtered element
> 
> at `pve-manager/www/manager6/qemu/NetworkEdit.js:83` and LXC (implicite true) there is `autoSelect: true` which is handled/overridden at `proxmox-widget-toolkit/src/form/ComboGrid.js:435`
> This makes searching impossible, because as soon as one character is typed, the first result is match.
> 
> What would be the recommended approach?
> 
> Thanks,
> 
> Goofy
> 
> 
> 
> 
> 
Hi and thanks for wanting to contribute!

I had a short look and it seems that there are some issues with this in 
our ComboGrid implementation.

The 'autoSelect' actually does two things:

* extjs selects the first entry when the picker is opened
* the combogrid selects the first entry from the store on the first load

The issue here is that the autoselect behavior from extjs causes
the first entry in the grid to be selected, which steals
the focus from the actual field, and this triggers the validator
(which is not valid when one has only types a single character most of 
the time)

I have to think about this a bit how to solve it, but maybe we have
to teach the combogrid to not take the focus away from the field
when the first item is selected?

I'll try to see what i can do here, but would you mind opening
a bug for your features in the meantime:

https://bugzilla.proxmox.com

i'd update it then with this info and when
the underlying issues are resolved.
(not sure how long that takes though...)


Simply disabling autoSelect is not really what we want here, because
of the second behavior i mentioned above.