From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 35F351FF134 for ; Wed, 15 Jul 2026 09:42:37 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 3E5E82141C; Wed, 15 Jul 2026 09:42:36 +0200 (CEST) Message-ID: <81fc6234-10c8-4641-b9f9-e6f5d5b7a461@proxmox.com> Date: Wed, 15 Jul 2026 09:42:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: ui: make selection fields searchable To: 666Goofy666 <666goofy666@proton.me>, "pve-devel@lists.proxmox.com" References: Content-Language: en-US From: Dominik Csapak In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1784101332861 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.340 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: U5PEMU4P3CHSL5ZKA5VAANXPM7FUP5FH X-Message-ID-Hash: U5PEMU4P3CHSL5ZKA5VAANXPM7FUP5FH X-MailFrom: d.csapak@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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.