Closed
Bug 765618
Opened 13 years ago
Closed 9 years ago
nsILoadGroup.requests are not always nsIRequest
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 896666
People
(Reporter: jari.bakken, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.27 Safari/536.11
Steps to reproduce:
The docs for nsILoadGroup (https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsILoadGroup) appear to guarantee that the "requests" attribute will return an enumerator of type nsIRequest, but it seems the iterator may in some cases also include WebSockets.
See http://code.google.com/p/selenium/issues/detail?id=3686 for the original bug report against WebDriver's FirefoxDriver.
Expected results:
I'm not sure if this is bug in the docs or in the code.
Updated•13 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Updated•12 years ago
|
Component: Untriaged → XPCOM
Product: Firefox → Core
Updated•12 years ago
|
Component: XPCOM → Networking
Comment 1•12 years ago
|
||
A WebSocket is an nsIRequest... on the c++ side.
On the JS side it hides all the non-DOM bits, of course. That's arguably a bug; it should use a shim to do the nsIRequest bits. Or not have them at all, of course; I think the fact that websockets are in the loadgroup at all is a bug, possibly already filed.
Comment 2•12 years ago
|
||
Correct, that's bug 896666.
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•