From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id BF84A1FF139 for ; Tue, 24 Feb 2026 13:51:01 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7CD199AE0; Tue, 24 Feb 2026 13:51:54 +0100 (CET) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pve-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH widget-toolkit] fix regression in checkcolumn rendering Date: Tue, 24 Feb 2026 13:51:33 +0100 Message-ID: <177193748936.602062.3861563243470252510.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260224085733.594116-1-d.csapak@proxmox.com> References: <20260224085733.594116-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1771937494015 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.047 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: X62H47SSC72GKIYW43PWPMNWP3ZRDOCM X-Message-ID-Hash: X62H47SSC72GKIYW43PWPMNWP3ZRDOCM X-MailFrom: f.gruenbichler@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 Tue, 24 Feb 2026 09:55:22 +0100, 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. > > [...] Applied (+cherry-picked into stable-bookworm), thanks! [1/1] fix regression in checkcolumn rendering commit: fb8da23d5955780d0018d69305c87deb3ab3a596 Best regards, -- Fabian Grünbichler