Aborting a fetch can't stop a POST already running server-side, so a stale activation could still land last. Chain the requests so each runs after the previous resolves — the latest navigation's activation is always last. A 5s per-request timeout keeps a hung request from stalling the chain. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| app.js | ||
| webauthn.js | ||