From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 4A7B31FF13A for ; Wed, 27 May 2026 16:21:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A50051F22F; Wed, 27 May 2026 16:21:43 +0200 (CEST) From: Thomas Lamprecht To: yew-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH yew-widget-toolkit] widget: charts: map: update info location if page is scrolled Date: Wed, 27 May 2026 16:21:33 +0200 Message-ID: <177989169074.333541.2892993659274495816.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260527094043.1472756-1-d.csapak@proxmox.com> References: <20260527094043.1472756-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: 1779891674726 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 TVD_PH_SUBJ_META1 0.001 Email has a Phishy looking subject line Message-ID-Hash: 5ODFU5ATNWE6ES4BI2SIDAT3GBEEC2UZ X-Message-ID-Hash: 5ODFU5ATNWE6ES4BI2SIDAT3GBEEC2UZ 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 Wed, 27 May 2026 11:37:57 +0200, Dominik Csapak wrote: > When the map is part of a scrollable container and the info is shown, > scrolling the container does not move the info box. > > To fix that, install a capturing scroll event handler that triggers on > all scroll events on the page, and trigger an alignment update of the > info box. > > [...] Applied, thanks! [1/1] widget: charts: map: update info location if page is scrolled commit: dd1bffe928cbfebeac548012cd8ced3b2f5ddf4f