Closed
Bug 439286
Opened 17 years ago
Closed 8 years ago
make global name XMLHttpRequest available to JS components
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
DUPLICATE
of bug 1164188
People
(Reporter: ericjung, Unassigned)
References
Details
Currently, XPCOM components must instantiate XHR like so:
var req = Components.classes["@mozilla.org/xmlextras/xmlhttprequest;1"]
.createInstance(Components.interfaces.nsIXMLHttpRequest);
To be consistent with how XHR is typically used from chrome, and how XHR is used in web pages written for Firefox (that is, new XMLHttpRequest()), we should expose the XHR component to XPCOM components as XMLHttpRequest.
Please update http://developer.mozilla.org/en/docs/XMLHttpRequest#Using_from_XPCOM_components when complete.
See http://groups.google.com/group/mozilla.dev.extensions/tree/b
rowse_frm/thread/b7a4663fd8012c2c/44fb605233a66e9f?rnum=11&a
mp;_done=%2Fgroup%2Fmozilla.dev.extensions%2Fbrowse_frm%2Fth
read%2Fb7a4663fd8012c2c%2Fdb7a632de65bbf37%3Ftvc%3D1%26fwc%3
D1%26#doc_8010a139533bba08
|
Reporter | |
Updated•17 years ago
|
Summary: XHR should be exposed as → XHR should be exposed as "XMLHttpRequest" to XPCOM
|
|
Reporter | |
Updated•17 years ago
|
Summary: XHR should be exposed as "XMLHttpRequest" to XPCOM → XHR should be exposed as XMLHttpRequest to XPCOM
|
||
Updated•17 years ago
|
Component: XPCOM → XPConnect
QA Contact: xpcom → xpconnect
Summary: XHR should be exposed as XMLHttpRequest to XPCOM → make global name XMLHttpRequest available to JS components
|
||
Comment 2•8 years ago
|
||
Bug 1164188 supercedes this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•