From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Dominik Csapak" <d.csapak@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH widget-toolkit] fix regression in checkcolumn rendering
Date: Tue, 24 Feb 2026 10:45:01 +0100 [thread overview]
Message-ID: <DGN3G9E1OVJK.81QQ7XIRGXHQ@proxmox.com> (raw)
In-Reply-To: <20260224085733.594116-1-d.csapak@proxmox.com>
Gave this a quick spin since I was just encountering the missing
checkboxes. Checked the various places we're using checkcolumn and seems
to work as advertised.
Tested-by: Michael Köppl <m.koeppl@proxmox.com>
On Tue Feb 24, 2026 at 9:55 AM CET, Dominik Csapak wrote:
> in commit 57cd471f79ecd6b98c9cadb600ba0255360980fe the default column
> renderer was changed to Ext.htmlEncode, so that by default, we don't
> return raw HTML there anymore.
>
> The 'checkcolumn' relies on that behavior though, so we have to reset
> the renderer there to 'undefined' for it to work properly.
>
> This fixes all uses of 'checkcolumn', for example the enabled column in
> the boot order edit window for virtual machines.
>
> Fixes: 57cd471 (prevent interpreting of HTML in column grids by default)
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> src/Toolkit.js | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/src/Toolkit.js b/src/Toolkit.js
> index d4e579b..bdfadf8 100644
> --- a/src/Toolkit.js
> +++ b/src/Toolkit.js
> @@ -769,12 +769,21 @@ Ext.define('Proxmox.Cookies', {
>
> // Prevents html entities to be interpreted by the browser in grid columns by
> // default. Custom renderer have to take care of this by themselves.
> +//
> +// Reset the renderer for the 'checkcolumn' back to undefined, since it relies
> +// on the renderer returning raw HTML.
> Ext.define('Proxmox.grid.column.Column', {
> override: 'Ext.grid.column.Column',
>
> renderer: Ext.htmlEncode,
> });
>
> +Ext.define('Proxmox.grid.column.Check', {
> + override: 'Ext.grid.column.Column',
> +
> + renderer: undefined,
> +});
> +
> // force alert boxes to be rendered with an Error Icon
> // since Ext.Msg is an object and not a prototype, we need to override it
> // after the framework has been initiated
next prev parent reply other threads:[~2026-02-24 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 8:55 Dominik Csapak
2026-02-24 9:45 ` Michael Köppl [this message]
2026-02-24 12:51 ` applied: " Fabian Grünbichler
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=DGN3G9E1OVJK.81QQ7XIRGXHQ@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=d.csapak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.