- Shipped
- August 23, 2026 at 12:27 AM UTC
- Author
- kamo
- Commit
- 106afb2
Two reports, two different mistakes of mine. THE PATTERN WAS INVISIBLE. It painted behind the pane, and every pane surface — FeatureCard, LauncherParentCard, WidgetFrame — is frosted glass: backdrop-filter blur(12px) under a 58%-opaque white gradient. A flat colour survives that, because blurring a flat fill changes nothing. A fine repeating pattern does not: it becomes an even smudge and then fades to nothing under the white. PaneBrandLayer already documents this exact finding, in its own header, as the reason the org mark sits IN FRONT. I read that file while building and reasoned past it — "a texture belongs under the same surface its colour is under" is tidy and it is wrong. The layer moves to zIndex 1: in front of the glass, under the mark (2) and the chrome (3), so a pane wearing both shows the logo over the pattern rather than through it. Default opacity drops from 0.18 to 0.12, since in front of the glass what was a faint wash is now a graphic over the member's text. THE PASTELS DISAPPEARED on master notes and notes the member may not edit. Those panes pass no colour handler — a master note wears its organisation's colours by design — and the section simply did not render. That was fine when colour had its own button, because the whole button disappeared with it. Now one button carries colour, pattern and logo, so it still opens, and a missing section reads as the pastels having been taken away. The palette now always shows; when it is not the member's to set it is greyed with the reason under it. Same rule the widgets page already follows: a control that refuses to move must say why. Swatches gained their names while I was there — they were showing raw ids.