public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH widget-toolkit v4 6/8] add pmx-critical CSS class
Date: Fri,  5 Jun 2026 17:38:17 +0200	[thread overview]
Message-ID: <20260605153819.310048-7-m.koeppl@proxmox.com> (raw)
In-Reply-To: <20260605153819.310048-1-m.koeppl@proxmox.com>

This class simply defines the background color similar to pmx-hint, but
for more critical messages. The color used is the same as for invalid
rows, but use a separate class to ensure that background colors for
invalid rows and critical error messages can be changed independently.

Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
---
Added this because I wanted to avoid using the proxmox-invalid-row class
for something that is pretty much a pmx-hint with a different color.

 src/css/ext6-pmx.css                        |  4 ++++
 src/proxmox-dark/scss/proxmox/_general.scss | 15 +++++++++++----
 2 files changed, 15 insertions(+), 4 deletions(-)

diff --git a/src/css/ext6-pmx.css b/src/css/ext6-pmx.css
index d8d9b8d..a33e83f 100644
--- a/src/css/ext6-pmx.css
+++ b/src/css/ext6-pmx.css
@@ -6,6 +6,10 @@
     background-color: LightYellow;
 }
 
+.pmx-critical {
+    background-color: #f3d6d7;
+}
+
 .proxmox-tags-full .proxmox-tag-light,
 .proxmox-tags-full .proxmox-tag-dark {
     border-radius: 3px;
diff --git a/src/proxmox-dark/scss/proxmox/_general.scss b/src/proxmox-dark/scss/proxmox/_general.scss
index dcbf049..9eba060 100644
--- a/src/proxmox-dark/scss/proxmox/_general.scss
+++ b/src/proxmox-dark/scss/proxmox/_general.scss
@@ -39,12 +39,19 @@ div.eol-notice + div[id^="panel-"] > div[id^="panel-"][id$="-bodyWrap"] > div {
   background-color: $background-warning;
 }
 
-.pmx-hint a {
-  color: $highlighted-text-alt;
+.pmx-critical {
+  background-color: $background-invalid;
 }
 
-.pmx-hint a:active {
-  color: $highlighted-text;
+.pmx-hint,
+.pmx-critical {
+  a {
+    color: $highlighted-text-alt;
+
+    &:active {
+      color: $highlighted-text;
+    }
+  }
 }
 
 // Unclickable elements (mostly for elements with conditional handlers)
-- 
2.47.3





  parent reply	other threads:[~2026-06-05 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 15:38 [PATCH cluster/docs/manager/widget-toolkit v4 0/8] add warning messages for high token timeouts in clusters Michael Köppl
2026-06-05 15:38 ` [PATCH docs v4 1/8] asciidoc-pve: allow linking sections with get_help_link Michael Köppl
2026-06-05 15:38 ` [PATCH docs v4 2/8] pvecm: add info about warnings regarding token coefficient Michael Köppl
2026-06-05 15:38 ` [PATCH cluster v4 3/8] add functions to determine warning level for high token timeouts Michael Köppl
2026-06-05 15:38 ` [PATCH cluster v4 4/8] pvecm: warn users of high token timeouts when using status command Michael Köppl
2026-06-05 15:38 ` [PATCH cluster v4 5/8] api: join info: add totem timeout warning message and level Michael Köppl
2026-06-05 15:38 ` Michael Köppl [this message]
2026-06-05 15:38 ` [PATCH manager v4 7/8] ui: cluster info: move initialization of items to initComponent Michael Köppl
2026-06-05 15:38 ` [PATCH manager v4 8/8] ui: cluster info: display warnings from the join info endpoint Michael Köppl

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=20260605153819.310048-7-m.koeppl@proxmox.com \
    --to=m.koeppl@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal