Check whether the outcome improved
Run interruption boundaries
Download a patterned document and interrupt before a range, after an acknowledgment, at an exact boundary, and during the final remainder. Record retained length and expected next request before resuming each case.
Exercise stale and revised state
Resume from a partial file after a page revisit and after the selected document has a different revision. Verify identity checks prevent incompatible bytes from being appended, and confirm the documented restart path remains clear.
Compare final bytes
Byte-compare every completed result with a fresh full download, including length, content type, and document identity. Check the visible terminal state and ensure a partial or mismatched result cannot be offered as ready.
What to carry forward
Accept resume behavior when each interruption produces the expected range, source-equivalent bytes, and same-document identity across retries. Fail any gap, overlap, revision mix, or completion state that lacks content evidence, then retain the smallest patterned fixture.
Technical background: MDN reference.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow