From: Shannon Sterz <s.sterz@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [RFC yew-comp/yew-widget-toolkit/yew-widget-toolkit-assets 0/3] minor ui/ux tweaks for pwt and yew-comp
Date: Mon, 4 May 2026 16:39:08 +0200 [thread overview]
Message-ID: <20260504143911.288747-1-s.sterz@proxmox.com> (raw)
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.
the log view in the syslog and task log components was slightly tweaked to avoid
interference between scrollbars and drag handles.
mainly sending this as rfc for now to get feedback on how the dropdown/dropup
is handled here.
pwt-assets:
Shannon Sterz (1):
dropdown: add class for dropup mode
scss/_dropdown.scss | 4 ++++
1 file changed, 4 insertions(+)
pwt:
Shannon Sterz (1):
dropdown/align: make the picker render above or below a dropdown
src/dom/align.rs | 6 +++-
src/widget/dropdown.rs | 62 +++++++++++++++++++++++++++++++++++-------
2 files changed, 57 insertions(+), 11 deletions(-)
yew-comp:
Shannon Sterz (1):
task_viewer/syslog: make padding margin to improve ux
src/syslog.rs | 2 +-
src/task_viewer.rs | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Summary over all repositories:
5 files changed, 63 insertions(+), 13 deletions(-)
--
Generated by murpp 0.10.0
next reply other threads:[~2026-05-04 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 14:39 Shannon Sterz [this message]
2026-05-04 14:39 ` [PATCH yew-widget-toolkit-assets 1/3] dropdown: add class for dropup mode Shannon Sterz
2026-05-04 14:39 ` [PATCH yew-widget-toolkit 2/3] dropdown/align: make the picker render above or below a dropdown Shannon Sterz
2026-05-04 14:39 ` [PATCH yew-comp 3/3] task_viewer/syslog: make padding margin to improve ux Shannon Sterz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260504143911.288747-1-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=yew-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox