Disallow XHRs after unload
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- PR merge metrics
- PR metrics pending
Description
We ran into an edge case where calling XHR from within onabort handler of another XHR while navigating away -- causes a crash:
https://bugs.chromium.org/p/chromium/issues/detail?id=797675
https://chromium-review.googlesource.com/c/chromium/src/+/851113
Would we nice if the spec explicitly allows ignoring XHRs that are queued late in "end of life" -- such as after unload has fired.
Thoughts?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Chromium issue 797675 and Chromium change 851113, then locate the HTML Standard sections covering XHR and unload behavior. The issue needs a decided specification change defining whether late XHRs may be ignored after unload; completion would require agreement on and documenting that behavior in the standard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100