#552: a disabled dialog button looks disabled (v0.6.209) #562

Merged

Cordy merged 3 commits from fix-552d into main

2026-09-16 02:58:59 +00:00

Cordy commented

2026-09-16 02:53:58 +00:00

Owner

Found during the live pass over v0.6.208 on files-bao.

The collision check switches the primary button off correctly — verified in the page, gadd-go.disabled === true and gren-go.disabled === true on a clash. But the button carried on rendering as a solid, full-colour primary: getComputedStyle(btn).opacity === "1". It invites the click it is going to ignore.

Cause is scope, not logic. Every :disabled rule in index.html belonged to something else:

.pgn[disabled]                              { … }
.uabtn:disabled                             { opacity: .5; cursor: not-allowed; }
.uabtn:disabled:hover                       { … }
#adminview .verfoot button[disabled]        { opacity: .55; cursor: default; }

Dialog action buttons are none of those — .dlgactions button had no disabled styling at all, so the state was invisible in every dialog, not just the three the #552 check touches. It simply had not been visible before because nothing disabled a dialog button until v0.6.208.

The rule goes beside .dlgactions button.danger, the global dialog-button family de-scoped in v0.6.203, so the fix lands once for the whole app rather than per dialog — the same call taken then.

.dlgactions button:disabled { opacity: .5; cursor: not-allowed; }

Web suite green, node --check clean, rule asserted outside any @media block.

Found during the live pass over v0.6.208 on files-bao. The collision check switches the primary button off correctly — verified in the page, `gadd-go.disabled === true` and `gren-go.disabled === true` on a clash. But the button carried on rendering as a solid, full-colour primary: `getComputedStyle(btn).opacity === "1"`. It invites the click it is going to ignore. Cause is scope, not logic. Every `:disabled` rule in `index.html` belonged to something else: ``` .pgn[disabled] { … } .uabtn:disabled { opacity: .5; cursor: not-allowed; } .uabtn:disabled:hover { … } #adminview .verfoot button[disabled] { opacity: .55; cursor: default; } ``` Dialog action buttons are none of those — `.dlgactions button` had no disabled styling at all, so the state was invisible in **every** dialog, not just the three the #552 check touches. It simply had not been visible before because nothing disabled a dialog button until v0.6.208. The rule goes beside `.dlgactions button.danger`, the global dialog-button family de-scoped in v0.6.203, so the fix lands once for the whole app rather than per dialog — the same call taken then. ```css .dlgactions button:disabled { opacity: .5; cursor: not-allowed; } ``` Web suite green, `node --check` clean, rule asserted outside any `@media` block.

Cordy added 2 commits

2026-09-16 02:53:59 +00:00