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 860411FF146 for ; Tue, 09 Jun 2026 18:51:18 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 32C4919644; Tue, 9 Jun 2026 18:51:17 +0200 (CEST) From: Thomas Lamprecht To: yew-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH yew-widget-toolkit] touch: slidable: use bounding client rect for width Date: Tue, 9 Jun 2026 18:50:32 +0200 Message-ID: <178102383147.1897878.12397458006639184790.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260609071200.411677-1-d.csapak@proxmox.com> References: <20260609071200.411677-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: 1781023796659 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: P2QLRU3V2W7WYTJLO4JB2H3LT3IQ6GDC X-Message-ID-Hash: P2QLRU3V2W7WYTJLO4JB2H3LT3IQ6GDC 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: Yew framework devel list at Proxmox List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 09 Jun 2026 09:11:10 +0200, Dominik Csapak wrote: > when calculating the width of the left and right actions, using > offsetWidth is problematic since it's always returned as an integer[0]. > Since the browser calculates the sizes with fractional pixels, it can > happen that this is too narrow, impacting the flex layout. It'll always > be less than one pixel, but it can lead to e.g. text wrapping or similar > effects, disturbing the overall layout here. > > [...] Applied, thanks! [1/1] touch: slidable: use bounding client rect for width commit: f77f00eaf468551ecc0bd7e626b024e13d719951