Skip to content

v0.7.1 — client-initiated fetch aborts are not resource faults - #9

Open
geyutu6755 wants to merge 1 commit into
mainfrom
release/v0.7.1
Open

geyutu6755 wants to merge 1 commit into
mainfrom
release/v0.7.1

Conversation

@geyutu6755

Copy link
Copy Markdown
Owner

Special-audit follow-up to v0.7.0 (audit: resource dedup / fetch-XHR channels / form-button safety).

Fix

  • SPAs cancel in-flight API requests constantly (stale queries, route changes, timeouts). A cancelled fetch/XHR (net::ERR_ABORTED) is application behaviour, not a page fault — no longer reported as resource-load-failure.
  • Real network failures on fetch/XHR (connection refused / DNS / reset / destroyed socket) are STILL reported; aborted subresources (img/script) keep coverage.

Evidence

  • New regression test pair (TDD): client abort → 0 findings; socket-destroyed fetch → finding present
  • Real audit site: 9 → 8 findings, all planted scenarios still detected (7 verified + 1 suspected)
  • Full suite 186/186; npm audit 0
  • Also: corrected issues.md verified/suspected wording; CI Chromium install retries once on CDN drops

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant