docs: correct specificity arithmetic and spinner-clause accuracy in .dd-accent-icon comments

Glyph rule is (0,3,0) > (0,1,0) — beats .mud-secondary-text on specificity, not source order.
ReleaseHeroOverlay spinner comment now distinguishes dead glyph clauses from the live spinner clause that produced the intentional light delta.
This commit is contained in:
daniel-c-harvey
2026-06-20 02:32:12 -04:00
parent 2fbb1c9b95
commit c28a2b1cf5
4 changed files with 11 additions and 8 deletions
@@ -769,10 +769,10 @@ body:has(.waveform-visualizer-control-overlay) {
.mud-secondary-text on the inner .mud-icon-root <svg>, and that rule is `!important`
(color: var(--mud-palette-secondary) !important). Targeting only the .mud-icon-button
wrapper therefore never wins — the svg keeps its own !important colour. The documented
override bug. To beat an !important declaration we need our own !important AND equal-or-
higher specificity: .dd-accent-icon .mud-icon-root (0,2,0) ties .mud-icon-root.mud-
secondary-text (0,2,0) and wins on source order (deepdrft-styles.css is linked LAST in
App.razor, after MudBlazor + isolated CSS). The .mud-icon-button selector carries the
override bug. The glyph clause .dd-accent-icon .mud-icon-button .mud-icon-root is
specificity (0,3,0) + !important, which beats MudBlazor's standalone .mud-secondary-text
(0,1,0) + !important on specificity alone — source order is not load-bearing for the
glyph clause. The .mud-icon-button selector carries the
Color.Inherit affordances (lava-lamp glyph inherits the wrapper colour, no
.mud-secondary-text to fight); the spinner covers the PlayStateIcon loading state.