Closed Bug 572631 Opened 14 years ago Closed 13 years ago

e10s HTTP: provide TabParent to HTTP channel clients

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: jduell.mcbugs, Unassigned)

References

Details

Dave Dahl tells me that some Firebug work needs to be able to associate HTTP channels with tabs in order to show per-tab activity instead of a single global log.

It sounds like perhaps the TabParent that we'll be associating with channels as part of bug 569227 can perhaps provide what he needs.  We'd need to figure out exactly what that is (Dave? How about an nsIDOMWindow?), and which interface to use to export it.
After chat with Dave, I understood he needed imgIRequest provide the TabParent somehow (through some interface).  To achieve that we need some public accessor on the channel anyway.  Let's do both in this bug.
Can't we just hand out the TabParent from the nsILoadContext on the channel?
Is this still needed?
closed unless Dave tells me there's still a need here.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.