From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yew-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id A28731FF13C
	for <inbox@lore.proxmox.com>; Thu, 02 Apr 2026 12:28:45 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id AF21F11C06;
	Thu,  2 Apr 2026 12:29:14 +0200 (CEST)
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Thu, 02 Apr 2026 12:28:40 +0200
Message-Id: <DHILJU4Z91VE.3GS3O1SFZN4QV@proxmox.com>
Subject: Re: [PATCH yew-comp] wizard: make content panel resizable too if
 wizard parent is
From: "Christoph Heiss" <c.heiss@proxmox.com>
To: "Dominik Csapak" <d.csapak@proxmox.com>
X-Mailer: aerc 0.21.0
References: <20260401143416.2144615-1-c.heiss@proxmox.com>
 <68c42b44-f869-4054-9076-4091b51c3a9e@proxmox.com>
In-Reply-To: <68c42b44-f869-4054-9076-4091b51c3a9e@proxmox.com>
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1775125662202
X-SPAM-LEVEL: Spam detection results:  0
	AWL                    -1.440 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
	RCVD_IN_VALIDITY_CERTIFIED_BLOCKED      1 ADMINISTRATOR NOTICE: The query to
 Validity was blocked.  See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
	RCVD_IN_VALIDITY_RPBL_BLOCKED      1 ADMINISTRATOR NOTICE: The query to
 Validity was blocked.  See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
	RCVD_IN_VALIDITY_SAFE_BLOCKED      1 ADMINISTRATOR NOTICE: The query to
 Validity was blocked.  See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
	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: JISCQTKG3D6OXDYES3LUSXWX3AM53LE3
X-Message-ID-Hash: JISCQTKG3D6OXDYES3LUSXWX3AM53LE3
X-MailFrom: c.heiss@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
CC: yew-devel@lists.proxmox.com
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Yew framework devel list at Proxmox <yew-devel.lists.proxmox.com>
List-Help: <mailto:yew-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:yew-devel-owner@lists.proxmox.com>
List-Post: <mailto:yew-devel@lists.proxmox.com>
List-Subscribe: <mailto:yew-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:yew-devel-leave@lists.proxmox.com>

On Thu Apr 2, 2026 at 8:27 AM CEST, Dominik Csapak wrote:
> didn't test it, but is there any argument against always
> setting that class?

Was a bit reluctant to do that in case there is some weird interaction
somewhere else, as I'm not super deep into yew-{comp/pwt}.

Did a quick test though, at least for only existing wizard (PDM remotes)
it doesn't seem to change anything (kinda expected, I guess).

I'll send a v2 setting it unconditionally, if nothing else speaks
against it.