[whatwg/xhr] Synchronous send() can report timing with null reporting steps after timeout (Issue #412)

Lubrsi created an issue (whatwg/xhr#412)

### What is the issue with the XMLHttpRequest Standard?

In synchronous [send()](https://xhr.spec.whatwg.org/#the-send()-method), step 12.6 terminates the fetch on timeout, and step 12.7 unconditionally reports timing.

  Fetch’s [report timing](https://fetch.spec.whatwg.org/#finalize-and-report-timing) starts with:

  > Assert: controller’s report timing steps is non-null.

  Those steps are initialized by processResponseEndOfBody in [fetch response handover](https://fetch.spec.whatwg.org/#fetch-finale). A sync XHR in a worker can time out before that initialization, tripping the assertion.

  Should timing reporting be skipped in this case, or should Fetch initialize the reporting steps on termination?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/412
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/xhr/issues/412@github.com>