The header and composer were full-bleed bands (flush to the top/right/bottom viewport edges, composer corners off-screen) next to a rail that floats with a 12px margin. The new --layout-gutter (12px) spaces the rail, header, empty-state card and composer identically on every side; --radius-panel/-control/-chip (-pill) replace the ad-hoc radii across the shared classes, so every panel is rounded on all four corners and shared controls match in every theme. The desktop-only ::after hairlines and the left-corner-only radius are gone. Aero: the rail and the chat chrome (answers included) share one even recipe - the wallpaper extra-blurred into a hue-free wash (background-glass.webp) under a uniform ~50% white veil and a whisper of gloss. Measured within ~10 RGB units across the rail top->bottom and the card/composer left->right; the blue->green smear and the teal composer are gone. The composer's field is a clean even tile with no wallpaper gradient inside it. Chat fixes: send is a filled primary tile shaped exactly like attach (dimmed while the input is empty), suggestion/context chips use the shared .chip token (40/44px target, visible rim, full-contrast text, raw model id in the tooltip), the AI note reads at 12px --text-muted (.ai-disclaimer), the selected sidebar row carries the accent border + accent icon, the theme toggle is back in Aero (the moon flips to Dark; Settings brings Aero back), and the empty state is centered exactly between header and composer. Outside CSS: the wallpaper's top-left HUD-circle decoration (it peeked through the 12px gutters on wide windows) was healed out of background.webp and background-blur.webp; the orbs/bubbles ride one masked .ice-floats layer that fades them under the chrome bands and the rail strip, so none is sliced by a panel edge (still parked under reduced motion). Version 0.6.0, SW -> freezmo-v82. Tests: chat suite pins the new geometry (12px gutter, 24px corners, even wash on all four panels, send-vs-attach shape, chips/input radii); mobile pins the phone chrome and the Aero toggle; bubbles pins the floats layer + its reduced-motion opt-out. |
||
|---|---|---|
| .. | ||
| bubble-perf.mjs | ||
| bubbles-test.mjs | ||
| chat-test.mjs | ||
| contrast.mjs | ||
| freeze-loading-test.mjs | ||
| i18n-test.mjs | ||
| lib.mjs | ||
| mobile-test.mjs | ||
| model-compare.mjs | ||
| native-test.mjs | ||
| phase1-test.mjs | ||
| phase2-test.mjs | ||
| phase3-test.mjs | ||
| providers-test.mjs | ||
| README.md | ||
| regression.mjs | ||
| review-test.mjs | ||
| run-all.mjs | ||
| security-test.mjs | ||
| wizard-test.mjs | ||
Browser suites
End-to-end checks for Freezmo, driven by Playwright against a running
production build. Everything lives in this repo (nothing in /tmp), so a
reboot cannot wipe the harness.
Requirements
- The app is running on
http://127.0.0.1:3207(systemctl --user start freezmo). - A Chromium build. The suites auto-detect the newest Playwright Chromium in
~/.cache/ms-playwright/; override withCHROME=/path/to/chrome. npm install(dev deps:playwright-core,axe-core).
Running
npm run build && systemctl --user restart freezmo # fresh build first
npm run test:e2e # every suite, in order
npm run test:e2e -- phase1 # only suites whose name contains "phase1"
Each suite prints PASS/FAIL lines and exits non-zero on failure; the runner
prints a per-suite summary at the end.
Suites
| Suite | Covers |
|---|---|
regression.mjs |
Library, deck card + menu, study feed to results, homework entry, desktop shell + settings/health panel. |
bubbles-test.mjs |
Ice-scene bubbles: stacking/layout contract, keyframes only transform+opacity, rise/sway/scale/fade phases, per-breakpoint counts (5/3/2), phone pacing, reduced motion, tab-hidden parking. |
mobile-test.mjs |
Five-tab bar at 360/390 × EN/CS × dark/light × reduced motion (labels, targets, no hamburger/drawer), the library ⋯ sheet (Import JSON / New folder), the settings sheet (touch targets, key flow, drag-to-close, backdrop), axe contrast audits. |
wizard-test.mjs |
Deck 3-step flow and homework flow, flat action bar, in-page mode switch, the loading lock, abort-on-leave. |
native-test.mjs |
Manifest/PWA head, offline banner + disabled generate, share target GET + POST, Back-gesture layers, undo toast, tab re-tap, haptics, draft restore. |
i18n-test.mjs |
EN/CS dictionary parity, locale switch, Czech desktop shell, Czech phone tab labels and plurals. |
freeze-loading-test.mjs |
The generation loading screen appears immediately, hides the action bar, Cancel returns with the notice. |
review-test.mjs |
Smart Review loading feedback under a stalled request, the session end-to-end, mistakes, and the health-probe cache. |
phase1-test.mjs |
Backup export/import, persistence row, nudge, encrypted sync (enable/join/push/delete + API validation), usage-limit handling (client + a stub Ollama). |
phase2-test.mjs |
Answer history + SRS from a real study run, review/mistakes, stats, exam mode, push reminders hidden without VAPID and validated with it. |
phase3-test.mjs |
Check my work (API + phone/desktop UI), follow-ups, guide step explain, turn-into-a-study-deck. |
chat-test.mjs |
Chat: streaming API (validation, allowlist, context travel, history window, thinking separation, usage-limit mapping), attachment extraction, entry points, streaming/stop, markdown + KaTeX, model/scope pickers, edit/regenerate, offline, reduced motion, plus history (IDB persistence, reload, rename/search/delete/undo, scope+model memory), assistant actions, the export payload and a two-device sync round-trip. |
Extra instances
phase1, phase2 and phase3 start their own next start instance with a
stub Ollama (or VAPID keys) on a spare port (3208/3209). Each suite checks the
port is free first and kills the whole process group on exit, so ports do not
leak between suites. Scratch data for the VAPID test lives in tests/.tmp/
(gitignored).
Diagnostics (not part of the run)
node tests/bubble-perf.mjs [label] measures the ice-scene frame cost with a
CDP performance trace (rAF frame timing, long tasks, main-thread busy time,
style recalcs) on a 4× throttled phone profile and a 2× desktop profile. It
always exits 0; the numbers are for tuning the bubble count/speed.