Skip to content

fix(#207): read all four overlay padding sides from the style - #208

Merged
octalide merged 1 commit into
devfrom
fix/207
Oct 3, 2026
Merged

octalide merged 1 commit into
devfrom
fix/207

Conversation

@octalide

@octalide octalide commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator

Closes #207

Plan

  • overlay.Chrome.pad becomes theme.Edges, read through context.px_edges like window padding.
  • Overlay origin, width and measured size use l/t/r/b, and toast cards use them too.
  • Built-in themes set pad to equal sides on overlay (0), tooltip and toast (theme pad), so their look is unchanged.
  • New test overlay__pads_each_side_from_its_style sets an asymmetric overlay.pad and checks box growth and content offset.

Ran mach test . (233 passed) and mach fmt . --check.

Chrome.pad is now theme.Edges and overlay sizing and toast cards use each
side, as window bodies do. Built-in themes set equal sides on overlay,
tooltip and toast, so their look is unchanged.
@octalide
octalide marked this pull request as ready for review October 3, 2026 02:55
@octalide
octalide merged commit 41a6ab5 into dev Oct 3, 2026
2 checks passed
@octalide
octalide deleted the fix/207 branch October 3, 2026 02:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: overlay padding uses one value for every side

1 participant