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 C20521FF13A for ; Wed, 27 May 2026 01:11:59 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8E340A8F6; Wed, 27 May 2026 01:11:59 +0200 (CEST) From: Thomas Lamprecht To: yew-devel@lists.proxmox.com, Shannon Sterz Subject: applied: [PATCH datacenter-manager/yew-comp/yew-widget-toolkit 0/3] minor ui/ux tweaks for pwt and yew-comp Date: Wed, 27 May 2026 01:11:14 +0200 Message-ID: <177983705965.3227204.8525638904633186416.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260506095525.114495-1-s.sterz@proxmox.com> References: <20260506095525.114495-1-s.sterz@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: 1779837059631 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: F2KLLNGN423QXERFE3FIPBUAXE3B2FX5 X-Message-ID-Hash: F2KLLNGN423QXERFE3FIPBUAXE3B2FX5 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, 06 May 2026 11:55:22 +0200, Shannon Sterz wrote: > this series includes two minor tweaks that should improve the usability and > user experience of some yew components. > > dropdowns should now render their pickers below or above the component > depending on the size of the picker and available screen space. a dropup mode > improves usability for filter fields when the picker is rendered above the > dropdown. > > [...] Applied, thanks! [1/1] dropdown/align: make the picker render above or below a dropdown commit: e4c30c80e2c524be25003759e9263d84c2889440