paliad

m/paliad

Fork 0

Author	SHA1	Message	Date
mAi	4cd2f05d33	fix(dashboard): t-paliad-238 — hidden widgets render at proper size in edit mode Symptom (m, 2026-05-22): "super slim columns which I can move but not resize - and they seem greyed out." Hidden widgets in edit mode were rendering as 1×1 slivers because applyLayout left their inline grid- column empty — placeWidgets skipped non-visible entries entirely, so CSS Grid auto-flowed them into the next free cell at 1/12th width. The greyed-out + no-resize-handle parts were correct UX signalling that the widget is hidden; the slim rendering was the bug. Fix: - placeWidgets() gains a {includeHidden} option. When true, a second pass places hidden widgets after the visible pass — collision-aware + cursor-aware so the hidden tray stacks below the active layout without ever displacing a visible widget. applyLayout() passes includeHidden:true in edit mode. - materializePositions() keeps the default (hidden widgets retain their stored coordinates so un-hiding restores them in place). Server-side recovery (belt-and-braces): - SanitizeForRead now also clamps each widget's W/H/X against the catalog Min/Max + grid bounds on load. Stale rows with W below MinW (or above MaxW, or X+W overflowing the grid) heal on the next /api/me/dashboard-layout GET and the cleaned spec is persisted back. W=0 stays 0 (auto/default sentinel — the placer expands it). - The validator stays strict on write; the read-path sanitiser only exists to recover users who got into a bad state under the old rules. Tests: - bun: 4 new cases in dashboard-grid.test.ts pin includeHidden behaviour (hidden skipped by default, two-pass ordering, multi- hidden, no-overlap invariant). - go: 7 sub-tests in dashboard_layout_spec_test.go cover each SanitizeForRead clamp (MinW, MaxW, grid-width, MaxH, X+W overflow, W=0 sentinel, negative X) plus a round-trip Validate guarantee.	2026-05-22 15:53:19 +02:00

Author

SHA1

Message

Date

mAi

4cd2f05d33

fix(dashboard): t-paliad-238 — hidden widgets render at proper size in edit mode

Symptom (m, 2026-05-22): "super slim columns which I can move but not
resize - and they seem greyed out." Hidden widgets in edit mode were
rendering as 1×1 slivers because applyLayout left their inline grid-
column empty — placeWidgets skipped non-visible entries entirely, so
CSS Grid auto-flowed them into the next free cell at 1/12th width.
The greyed-out + no-resize-handle parts were correct UX signalling
that the widget is hidden; the slim rendering was the bug.

Fix:
- placeWidgets() gains a {includeHidden} option. When true, a second
  pass places hidden widgets after the visible pass — collision-aware
  + cursor-aware so the hidden tray stacks below the active layout
  without ever displacing a visible widget. applyLayout() passes
  includeHidden:true in edit mode.
- materializePositions() keeps the default (hidden widgets retain
  their stored coordinates so un-hiding restores them in place).

Server-side recovery (belt-and-braces):
- SanitizeForRead now also clamps each widget's W/H/X against the
  catalog Min/Max + grid bounds on load. Stale rows with W below MinW
  (or above MaxW, or X+W overflowing the grid) heal on the next
  /api/me/dashboard-layout GET and the cleaned spec is persisted
  back. W=0 stays 0 (auto/default sentinel — the placer expands it).
- The validator stays strict on write; the read-path sanitiser only
  exists to recover users who got into a bad state under the old
  rules.

Tests:
- bun: 4 new cases in dashboard-grid.test.ts pin includeHidden
  behaviour (hidden skipped by default, two-pass ordering, multi-
  hidden, no-overlap invariant).
- go: 7 sub-tests in dashboard_layout_spec_test.go cover each
  SanitizeForRead clamp (MinW, MaxW, grid-width, MaxH, X+W overflow,
  W=0 sentinel, negative X) plus a round-trip Validate guarantee.

2026-05-22 15:53:19 +02:00

Compare commits

1 Commits

d5b3652963 ... 4cd2f05d33

Diff Content Not Available

Compare commits

1 Commits d5b3652963 ... 4cd2f05d33

Diff Content Not Available

1 Commits

d5b3652963 ... 4cd2f05d33