From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pmg-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
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 [thread overview]
Message-ID: <178110246578.4116525.5968351076502241878.b4-ty@b4> (raw)
In-Reply-To: <20260610123916.2651267-1-d.csapak@proxmox.com>
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
prev parent reply other threads:[~2026-06-10 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 12:39 [PATCH pmg-yew-quarantine-gui/yew-widget-toolkit 0/2] pmg mobile quarantine: work around weird chrome behavior in slidable Dominik Csapak
2026-06-10 12:39 ` [PATCH yew-widget-toolkit 1/2] slidable: revert markup with old `x_actions` interface Dominik Csapak
2026-06-10 12:39 ` [PATCH pmg-yew-quarantine-gui 2/2] spam list: use new slidable interface Dominik Csapak
2026-06-10 14:42 ` Thomas Lamprecht [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=178110246578.4116525.5968351076502241878.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pmg-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