2.0 KiB
2.0 KiB
id, title, status, wave, depends_on, plan, spec
| id | title | status | wave | depends_on | plan | spec |
|---|---|---|---|---|---|---|
| walkthrough-navigation-layout-01 | Stable navigation footer | done | 1 | plan.md | ../../specs/ui/requirements/walkthrough-navigation-layout.md |
Task 01: Stable navigation footer
Acceptance
- The open walkthrough gives its explanation an internal scroll region and keeps its Previous/Next footer in a stable final-card position while steps change.
- The desktop floating window remains draggable; the phone bottom sheet keeps its navigation visible, reachable, and inside the dynamic viewport.
- Desktop and
mobile-chromeE2E coverage prove the navigation geometry with step changes and retain the existing walkthrough progression behavior.
Verification
(
set -e
cd apps/web
pnpm e2e:run tests/review/walkthrough.spec.ts
pnpm e2e:run tests/review/mobile-walkthrough.spec.ts -- --project=mobile-chrome
)
Files likely touched
apps/web/components/diff/walkthrough-step-card.tsxapps/web/components/diff/walkthrough-floating-window.tsxapps/web/e2e/tests/review/walkthrough.spec.tsapps/web/e2e/tests/review/mobile-walkthrough.spec.ts
Dependencies
None.
Parallelism
Sequential; the regression tests and shared walkthrough components change together.
Inputs
- Stable Walkthrough Navigation spec
- Fix plan
- Existing
WalkthroughFloatingWindowmobile bottom-sheet and desktop drag behavior.
Output contract
Report the failing regression-test evidence, implementation files, focused desktop/mobile E2E results, visual verification, risks, and updated task/plan status.
Completion record
- Desktop and
mobile-chromewalkthrough E2E passed with stable navigation geometry assertions. - Fresh synthetic desktop and mobile captures confirmed the footer is visible, reachable, and does not overlap the viewport edge.
- The remaining risk is browser-specific safe-area behavior; the floating
surface reserves
safe-area-inset-bottomfor the navigation footer.