Files
kandev/docs/plans/app-status-bar/task-07-mobile-status-e2e.md
T
José Almeida 9c16d337a2 feat(web): add global app status surface (#1869)
* feat(web): add app status bar

* feat(web): add app status bar visibility toggle

* feat(web): persist status bar item order

* fix(web): refine app status bar behavior

* fix(web): polish app status bar presentation

* test(web): split plugin slot coverage groups

* fix(web): address status surface review feedback

* fix(web): stabilize status bar overlay tests
2026-07-23 12:28:54 +01:00

1.2 KiB

id, title, status, wave, depends_on, plan
id title status wave depends_on plan
app-status-bar-07 Prove mobile Status drawer parity done 4
app-status-bar-04
app-status-bar-06
docs/plans/app-status-bar/plan.md

Prove mobile Status drawer parity

Inputs

Spec scenarios; mobile UI language; tasks 04 and 06; configured Pixel 5 project.

Files

  • apps/web/e2e/tests/plugins/mobile-status-drawer.spec.ts
  • Existing mobile helpers/page objects only when strictly needed.

Acceptance

  1. Mobile E2E installs fixture, opens Status from Home, task bottom navigation, and PageTopbar route, then sees built-ins plus plugin contribution with mobile-drawer props.
  2. Test proves dismiss/focus return, 44 px trigger, safe-area clearance, one internal scroll owner, zero document horizontal overflow, and no persistent second footer.
  3. Existing task navigation still works after drawer dismissal.

Verification

make build-web
cd apps/web && pnpm e2e:run tests/plugins/mobile-status-drawer.spec.ts -- --project=mobile-chrome

Output contract

Report mobile assertions, screenshot/rendered check, build/E2E result, blockers, and task status.