docs(backlog): file #152 — generated waybar height + right-edge icon spacing
All checks were successful
Check / eval (push) Successful in 4m1s
All checks were successful
Check / eval (push) Successful in 4m1s
Bernardo, filed live: the generated bar (non-whole-swap themes) should be a bit taller so the selected-workspace highlighter stops overflowing it, and the right module cluster needs consistent icon spacing + end padding (power currently sits too close to the screen edge). Full §3 visual protocol when taken. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -89,6 +89,24 @@ rofi#2317, and take the fix when a release carries it. If it is still open at
|
||||
the next lock bump, that is fine — nothing here rots meanwhile.
|
||||
*Last checked 2026-07-17: open, no maintainer response, no linked PR.*
|
||||
|
||||
### 152. Generated waybar polish: bar height vs workspace highlighter, right-edge icon spacing
|
||||
|
||||
Bernardo, 2026-07-17. Two visual fixes to the **generated** bar (the one
|
||||
every theme without a `waybar.jsonc`/`waybar.css` whole-swap gets — the
|
||||
4 whole-swap themes are out of scope unless the parity rule drags them in):
|
||||
- **Bar height:** make the bar a bit taller so the selected-workspace
|
||||
highlighter no longer renders taller than the bar itself (today it
|
||||
visually overflows/clips the bar edge).
|
||||
- **Right-module spacing:** the icon distances on the right cluster look
|
||||
uneven — e.g. the power button sits too close to the screen edge; give
|
||||
the cluster consistent inter-icon spacing and sane end padding.
|
||||
|
||||
This is §3 visual-protocol work (agent/THEME-DESIGN.md + VERIFICATION §3):
|
||||
before/after screenshots, two themes (one generated palette + one
|
||||
whole-swap for the no-regression side), scripted checks first, actually
|
||||
view the captures. Waybar CSS ↔ tray-menu gotchas in agent/MEMORY.md
|
||||
apply (never scope `*`).
|
||||
|
||||
### 151. `[human]` v1 launch plan — devise with Bernardo (includes the GitHub move)
|
||||
|
||||
Bernardo, 2026-07-17: before tagging v1, sit down and devise the launch plan.
|
||||
|
||||
Reference in New Issue
Block a user