From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 0/2] ui: ceph: improve discoverability of warning details
Date: Wed, 22 Feb 2023 10:36:53 +0100 [thread overview]
Message-ID: <20230222093655.2645787-1-a.lauterer@proxmox.com> (raw)
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
This will hopefully reduce the time spent on figuring out what exactly
is wrong and how one can fix it.
Aaron Lauterer (2):
ui: ceph: make the warning detail button stand out more
ui: ceph status: add tooltip with details to warnings
www/manager6/ceph/Status.js | 97 ++++++++++++++++++++++++++-----------
1 file changed, 70 insertions(+), 27 deletions(-)
--
2.30.2
next reply other threads:[~2023-02-22 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 9:36 Aaron Lauterer [this message]
2023-02-22 9:36 ` [pve-devel] [PATCH manager 1/2] ui: ceph: make the warning detail button stand out more Aaron Lauterer
2023-03-02 13:15 ` Dominik Csapak
2023-02-22 9:36 ` [pve-devel] [PATCH manager 2/2] ui: ceph status: add tooltip with details to warnings Aaron Lauterer
2023-02-22 9:39 ` [pve-devel] [PATCH manager follow-up " Aaron Lauterer
2023-03-02 13:15 ` Dominik Csapak
2023-03-02 13:22 ` Aaron Lauterer
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=20230222093655.2645787-1-a.lauterer@proxmox.com \
--to=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