If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Documentation incorrect for nsIXMLHttpRequestEventTarget timeout

RESOLVED FIXED

Status

Developer Documentation
API: DOM
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: Scott Turner, Assigned: chandrakm)

Tracking

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130409194949

Steps to reproduce:

The documentation for XMLHttpRequest is confusing.  It doesn't clearly explain what happens when a request reaches its timeout value.  It's reasonable to assume that timeout would raise an "error" event or possibly an "abort" event.  In fact, it raises a "timeout" event.  This behavior isn't documented anywhere.



Expected results:

Change https://developer.mozilla.org/en-US/docs/DOM/XMLHttpRequest and/or https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIXMLHttpRequestEventTarget to indicate that timeout causes a "timeout" event without any other event.

Updated

4 years ago
Assignee: nobody → bruant.d
Component: Untriaged → DOM
Product: Firefox → Developer Documentation
Version: 20 Branch → unspecified
(Assignee)

Comment 1

4 years ago
Added this "when a request reaches its timeout value  a "timeout" event is raised." in the help page for XMLHttpRequest at  https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest
(Assignee)

Comment 2

4 years ago
I am not sure, if i have the permission to change this bug status to resolved, some one who has the permission can change this to resolved.

Comment 3

4 years ago
(In reply to chandrakm from comment #2)
> I am not sure, if i have the permission to change this bug status to
> resolved, some one who has the permission can change this to resolved.
Yep. Thanks for your contribution.
Assignee: bruant.d → chandrakm
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

4 years ago
Thanks, Chandra!
You need to log in before you can comment on or make changes to this bug.