From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id B11FC1FF0BC for ; Thu, 15 Oct 2026 22:02:47 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id CB0BE2138C; Thu, 15 Oct 2026 22:02:45 +0200 (CEST) From: Thomas Lamprecht To: yew-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH yew-widget-toolkit] fix #8057: correctly scroll on firefox with submenus Date: Thu, 15 Oct 2026 22:02:30 +0200 Message-ID: <179209454901.3174600.6173863303284371255.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260921074926.852370-1-d.csapak@proxmox.com> References: <20260921074926.852370-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: 1792094561321 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.544 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: RO6KZ2WP2JLM5HSQON6FAA64BK5EQ4BD X-Message-ID-Hash: RO6KZ2WP2JLM5HSQON6FAA64BK5EQ4BD 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 Mon, 21 Sep 2026 09:49:20 +0200, Dominik Csapak wrote: > There is a subtle difference in calculating the height of nested > grid containers: chrome uses the min-content height while firefox does > not. This means, on firefox, the navigation drawer would not have it's > intended size + scrollbars, but would clip the submenus since they would > shrink. > > Fix this by giving the whole menu a container that can grow, and only > scroll the outer container. > > [...] Applied, thanks! [1/1] fix #8057: correctly scroll on firefox with submenus commit: 3bd425203ec34aa78ea71ac492ff7f763f33b11f