From: Dominik Csapak <d.csapak@proxmox.com>
To: Elias Huhsovitz <e.huhsovitz@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager 4/4] fix #6211: ui: vm: options:
Date: Fri, 10 Jul 2026 09:08:34 +0200 [thread overview]
Message-ID: <76ff06a5-9653-47d9-a006-1f7192fdc08b@proxmox.com> (raw)
In-Reply-To: <20260708130453.166084-5-e.huhsovitz@proxmox.com>
same here regarding the commit subject as 3/4
IMO this patch does not really fit together with the
rest, even though the bug mentions both.
(should have be two issues i guess, but it doesn't matter)
one comment inline
with or without that changed (+ the commit subject fixed):
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
On 7/8/26 3:05 PM, Elias Huhsovitz wrote:
> The "protection" options was ambiguous.
> Add hint to briefly describe the feature.
> Add help button that points to Options section containing a description
> of the "protection" option.
>
> Signed-off-by: Elias Huhsovitz <e.huhsovitz@proxmox.com>
> ---
> www/manager6/qemu/Options.js | 25 +++++++++++++++++++------
> 1 file changed, 19 insertions(+), 6 deletions(-)
>
> diff --git a/www/manager6/qemu/Options.js b/www/manager6/qemu/Options.js
> index 8a4721a0..664606da 100644
> --- a/www/manager6/qemu/Options.js
> +++ b/www/manager6/qemu/Options.js
> @@ -319,13 +319,26 @@ Ext.define('PVE.qemu.Options', {
> ? {
> xtype: 'proxmoxWindowEdit',
> subject: gettext('Protection'),
> + onlineHelp: 'qm_options',
> items: {
> - xtype: 'proxmoxcheckbox',
> - name: 'protection',
> - uncheckedValue: 0,
> - defaultValue: 0,
> - deleteDefaultValue: true,
> - fieldLabel: gettext('Enabled'),
> + xtype: 'inputpanel',
> + items: [
> + {
> + xtype: 'proxmoxcheckbox',
> + name: 'protection',
> + uncheckedValue: 0,
> + defaultValue: 0,
> + deleteDefaultValue: true,
> + fieldLabel: gettext('Enabled'),
> + },
> + {
> + xtype: 'displayfield',
> + userCls: 'pmx-hint',
> + value: gettext(
> + 'Prevents the VM and its disks from being removed',
> + ),
> + },
> + ],
instead of a new hint field, we could simply make use of the 'boxLabel'
here, which just shows extra text after the checkbox
but it's not a big deal either way
> },
> }
> : undefined,
prev parent reply other threads:[~2026-07-10 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 13:04 [PATCH docs/manager 0/4] manager/docs: fix: #6211: ui: docs: add reference to vm options protection/IDX/SEV Elias Huhsovitz
2026-07-08 13:04 ` [PATCH docs 1/4] qm_memory: update dead links in qm_memory_encryption_sev section on AMD SEV Elias Huhsovitz
2026-07-10 7:02 ` Dominik Csapak
2026-07-08 13:04 ` [PATCH docs 2/4] qm_memory: expand qm_memory_encryption documentation to include Intel TDX Elias Huhsovitz
2026-07-10 7:02 ` Dominik Csapak
2026-07-08 13:04 ` [PATCH manager 3/4] fix #6211: ui: vm: options: Elias Huhsovitz
2026-07-10 7:03 ` Dominik Csapak
2026-07-08 13:04 ` [PATCH manager 4/4] " Elias Huhsovitz
2026-07-10 7:08 ` Dominik Csapak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76ff06a5-9653-47d9-a006-1f7192fdc08b@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=e.huhsovitz@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox