#240 Flaky WebKit browser checks: a late request to the previous server, and aborted requests reported as errors
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#240
- issue
- state:closed
Two WebKit failures seen while getting #237 and #239 through CI. Neither PR caused them. 1. **accounts-browser.mjs:418** (CI, [job](https://github.com/openchronology/timeline-app/actions/runs/39380100165/job/118487019608)). After the native page switches to `second.example`, `requestsTo('https://timescale.info')` should be empty, but it had `timelines/00000000-0000-0000-0000-000000000001/revision`. A revision check for the first server's timeline went out after the switch. It may be a real bug: a live-update or Follow latest timer that isn't cancelled when the timeline changes servers. 2. **drafts-browser.mjs:277** (in a local Playwright container). `errors` had `…/api/timelines/00000000-0000-0000-0000-0000000000aa/query due to access control checks.` That's WebKit's message for a fetch cancelled by `page.goto`, reported as a page error. The fetch that was cut off should be ignored, or awaited before navigating. They pass on most runs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/issues/240