feat(ui): density toggle + readability/compact polish (LC-194) #240
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/lc-194-density-polish"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The concrete, testable core of the visual-polish pass: a persisted comfortable/compact density toggle (the named AC) mirroring the LC-191 theme infrastructure, plus a readability baseline.
What lands
users.densitycolumn (auth migration 0026, parallel tousers.theme) -comfortable(default/NULL) /compact; threaded throughUserRecord/User+set_user_density+User::density_or_default. 0026 added to the 22 hand-rolled auth-pool test files.base.htmlbootstrap also setsdata-densityfrom thelc-densitycookie / localStorage (default comfortable) before paint; exposeswindow.__lcSetDensityfor instant apply.resolve_localemiddleware cookie-sync is refactored into onesynchelper that stamps bothlc-themeandlc-densityfrom the saved prefs.settings-density/density-*keys in en + es.main.css):[data-density="compact"]tightens non-follow-up message rows (py-2rows; follow-ups arepy-0and excluded via:not, so no template edit) and inter-block markdown spacing.line-height: 1.5+ antialiasing, app-wide.Remaining LC-194 polish (continuing)
Larger-text setting; deeper sidebar / enclave-switcher hierarchy refinement; empty-state copy + illustrations; a formal elevation/shadow-token system. The density toggle + readability baseline are the bounded, testable slice; the rest is open-ended visual work to layer on.
Verification
just test+just test-saasgreen (theroutes_uploadsfailure under concurrent load is the documented flake - passes 12/12 run isolated; unrelated to this change).cargo fmt --allclean;i18n_cataloggate passes.