Hi all, first post. I ran into this on PVE 9.2.11 and it looks like a genuine regression in the dark theme rather than a deliberate choice, so I wanted to write it up.
In the dark theme, a grid row you have selected and a grid row your mouse is merely hovering over are rendered in exactly the same colour. In any guest list you cannot tell which VM or CT is actually selected. That matters because that grid is where you pick the target before hitting Shutdown or Remove.
The relevant line in /usr/share/javascript/proxmox-widget-toolkit/themes/theme-proxmox-dark.css is:
.x-grid-item-over,.x-grid-item-selected{background-color:#595959}
Both states get #595959. The row-lines variant a few rules later does the same thing.
What makes me think this is unintentional rather than a design decision is that the base ExtJS crisp theme underneath it does distinguish the two:
.x-grid-item-selected{color:#000;background-color:#c2ddf2}
.x-grid-item-over{color:#000;background-color:#e2eff9}
So upstream deliberately separates selected from hover, and the dark theme override collapses them. Contrast between the two states goes from 1.203:1 in the light theme to exactly 1.000:1 in the dark theme.
Reproduce: switch Color Theme to Proxmox Dark, open any node's guest list or a storage content list, click a row to select it, then move the mouse over a different row. Both rows look identical.
A minimal fix would be giving selected its own value and leaving hover as the lighter one, the same relationship the crisp theme uses. Something like keeping .x-grid-item-over at #595959 and moving .x-grid-item-selected to a distinct tone, or adding an inset left rail on the selected row so it does not rely on background alone.
Happy to file this on Bugzilla if that is the preferred channel, I just wanted to check here first in case it is known or intended.
For transparency, I found this while building a CSS theme of my own for the web UI, and I used an AI assistant while working on it, including for parts of this write up. The CSS values and reproduction steps above are from the shipped files on my own host and I have verified them directly.
In the dark theme, a grid row you have selected and a grid row your mouse is merely hovering over are rendered in exactly the same colour. In any guest list you cannot tell which VM or CT is actually selected. That matters because that grid is where you pick the target before hitting Shutdown or Remove.
The relevant line in /usr/share/javascript/proxmox-widget-toolkit/themes/theme-proxmox-dark.css is:
.x-grid-item-over,.x-grid-item-selected{background-color:#595959}
Both states get #595959. The row-lines variant a few rules later does the same thing.
What makes me think this is unintentional rather than a design decision is that the base ExtJS crisp theme underneath it does distinguish the two:
.x-grid-item-selected{color:#000;background-color:#c2ddf2}
.x-grid-item-over{color:#000;background-color:#e2eff9}
So upstream deliberately separates selected from hover, and the dark theme override collapses them. Contrast between the two states goes from 1.203:1 in the light theme to exactly 1.000:1 in the dark theme.
Reproduce: switch Color Theme to Proxmox Dark, open any node's guest list or a storage content list, click a row to select it, then move the mouse over a different row. Both rows look identical.
A minimal fix would be giving selected its own value and leaving hover as the lighter one, the same relationship the crisp theme uses. Something like keeping .x-grid-item-over at #595959 and moving .x-grid-item-selected to a distinct tone, or adding an inset left rail on the selected row so it does not rely on background alone.
Happy to file this on Bugzilla if that is the preferred channel, I just wanted to check here first in case it is known or intended.
For transparency, I found this while building a CSS theme of my own for the web UI, and I used an AI assistant while working on it, including for parts of this write up. The CSS values and reproduction steps above are from the shipped files on my own host and I have verified them directly.
