This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
nowhere in the specification is there language stating that a timeout event is fired (or at least I couldn't find it)
It is in fact defined: http://dvcs.w3.org/hg/xhr/raw-file/8d4e9ccfdbd4/Overview.html#timeout-error --- When something is said to be an timeout error run the request error steps for exception "TimeoutError" and event timeout. When something is said to be a request error for exception exception and event event run these steps: [...] 9. Fire a progress event named event.
(In reply to comment #1) > It is in fact defined: > http://dvcs.w3.org/hg/xhr/raw-file/8d4e9ccfdbd4/Overview.html#timeout-error > --- > > When something is said to be an timeout error run the request error steps for > exception "TimeoutError" and event timeout. > > When something is said to be a request error for exception exception and event > event run these steps: > > [...] > > 9. Fire a progress event named event. thanks for pointing that out; however, I see this does not use the formulaic language that is used in other event firing cases; namely, one of: (1) fire an event named X (2) fire a progress event named X for consistency, I would suggest changing the text to use one of the above forms
It does use that.
*** Bug 16305 has been marked as a duplicate of this bug. ***
ok, i see now it is parameterized via <em>event</em> variable in the "request error" sub-steps