From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 2E1201FF13A for ; Wed, 10 Jun 2026 16:44:37 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CDCFF12239; Wed, 10 Jun 2026 16:44:36 +0200 (CEST) From: Thomas Lamprecht To: pmg-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH pmg-yew-quarantine-gui/yew-widget-toolkit 0/2] pmg mobile quarantine: work around weird chrome behavior in slidable Date: Wed, 10 Jun 2026 16:42:01 +0200 Message-ID: <178110246578.4116525.5968351076502241878.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260610123916.2651267-1-d.csapak@proxmox.com> References: <20260610123916.2651267-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: 1781102595130 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 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: AJRRTOXY4NSKQUPZI33FGRHP4MTX53CT X-Message-ID-Hash: AJRRTOXY4NSKQUPZI33FGRHP4MTX53CT X-MailFrom: t.lamprecht@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 Mail Gateway development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 10 Jun 2026 14:39:08 +0200, Dominik Csapak wrote: > In the current version of the pmg mobile quarantine, chrome behaves weridly > with the slidable actions (not rendering text when it should). > > Probably a browser issue since it works in firefox, but sending two > patches that fix the problem. > > Either of the patches should be fine, so for now the pmg quarantine patch > is the easier way. But fixing it directly in pwt avoids having this issue > in the future (potentially). > > [...] Applied, split out the cargo.toml dependency update for pwt 0.8.8 to an upfront commit as the last bump already was build for that, so this here and the commit message was a bit confusing, thanks! Did also apply pwt, but not bump that one yet, as this isn't really used anywhere else (in our production UIs) yet. [1/1] spam list: use new slidable interface commit: cd12fab871a8028e216e9ae1d1c77606bc62ed2b [pwt]: [1/1] slidable: revert markup with old `x_actions` interface commit: 06d858f455dbc1993d622f96a7a5cdc8c40bd4d1