KeelrLeek
913289a297
Kyle put four crops side by side and asked why the top chrome disagrees with itself. The audit found five variants across three panel tops: the glass bar's arrows (28px circle, white, 17px glyph, 0.12 white-veil hover), the sidebar toggle and both Now Playing chevrons (28px 6px-radius squares, grey, 16px, opaque --bg-highlight hover that slabs under glass and a --glass-hover override that reads as nothing up here), the add-to-playlist trigger (grey square, 15px glyph), and the save button (34px 8px-radius square, 18px glyph). One spec now, the arrows' language: 28x28 circle, 16px glyph, #fff at rest, rgba(255,255,255,.12) hover in BOTH modes. This commit carries the Now Playing header set — np-icon (head collapse + rail expand), the plm-trigger override, and a new np-head override pulling SaveMenu's trigger down from its 34px playbar size (SaveMenu grows an iconSize prop; the playbar keeps 18, the head passes 16). The glass-hover overrides for these buttons are gone — the base veil is mode-independent — except one glass-scoped rule kept solely to outrank SaveMenu's own glass hover on specificity. The bar arrows' 17->16 and the sidebar toggle's disc ride the hub commit; their files carry that rework and split poorly. Verified by computed style across all five controls: identical to the pixel, and the disabled arrows stay dimmed white rather than grey so even the off state is the same hue family.