From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 manager 0/2] ui: ceph: improve discoverability of warning details
Date: Wed, 8 Mar 2023 17:05:50 +0100 [thread overview]
Message-ID: <82701573-4e32-550a-7842-d7b2b815754f@proxmox.com> (raw)
In-Reply-To: <20230308120919.1646218-1-a.lauterer@proxmox.com>
Am 08/03/2023 um 13:09 schrieb Aaron Lauterer:
> The goal for this small series is to make it easier/more obvious to see
> that there are potentially more details for a warning ceph is showing
> by:
> * having a tooltip with the details (limited in length)
> * making the detail/info button more visible
>
One bug I see is that if I open the detail window, the next extjs (probably store)
refresh seemingly refocuses the some part of the row and then the tooltip pops up
too for the element I'm already having the full detail window open.
That said, why not avoid the tooltip but inline the info by moving the severity to
the right, dropping the info button completely and making the grid row expandable,
i.e., like the PMG tracking center grid does?
Would feel more integrated and less duplicate (tooltip + detail window)
information.
next prev parent reply other threads:[~2023-03-08 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 12:09 Aaron Lauterer
2023-03-08 12:09 ` [pve-devel] [PATCH v3 manager 1/2] ui: ceph: make the warning detail button stand out more Aaron Lauterer
2023-03-08 12:09 ` [pve-devel] [PATCH v3 manager 2/2] ui: ceph status: add tooltip with details to warnings Aaron Lauterer
2023-03-08 16:05 ` Thomas Lamprecht [this message]
2023-03-08 16:38 ` [pve-devel] [PATCH v3 manager 0/2] ui: ceph: improve discoverability of warning details Aaron Lauterer
2023-03-08 16:43 ` Thomas Lamprecht
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=82701573-4e32-550a-7842-d7b2b815754f@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=pve-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