16306 2012-03-10 09:43:19 +0000 'timeout' event defined but never fired 2012-03-11 19:23:41 +0000 1 1 1 Unclassified WebAppsWG XHR unspecified PC All CLOSED WORKSFORME http://dvcs.w3.org/hg/xhr/raw-file/8d4e9ccfdbd4/Overview.html P2 normal --- 1 glenn annevk mike odinho public-webapps public-webapps-bugzilla oldest_to_newest 65286 0 glenn 2012-03-10 09:43:19 +0000 nowhere in the specification is there language stating that a timeout event is fired (or at least I couldn't find it) 65290 1 odinho 2012-03-10 10:06:40 +0000 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. 65296 2 glenn 2012-03-10 19:03:12 +0000 (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 65326 3 annevk 2012-03-11 17:04:20 +0000 It does use that. 65328 4 annevk 2012-03-11 17:04:58 +0000 *** Bug 16305 has been marked as a duplicate of this bug. *** 65329 5 glenn 2012-03-11 19:23:41 +0000 ok, i see now it is parameterized via <em>event</em> variable in the "request error" sub-steps