Closed Bug 964435 (jsplugins-streams) Opened 12 years ago Closed 7 years ago

[jsplugins] Allow capturing and re-using the initial plugin stream for jsplugins

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(e10s-)

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
e10s - ---

People

(Reporter: johns, Assigned: johns)

References

Details

JS implement plugins need to use XHR or other means to re-open the initial stream for the <object> tag. With Bug 558184, the <object> tag is aware of these plugins and we have a sane way to capture and re-use that stream.
Will this also fix bug 801406? That's high on my priority list!
I'm not sure exactly how this should work - ideally we could suspend mChannel until the JS plugin calls back requesting it (to avoid requiring sync JS load), but I'm not sure if the networking code supports that. If it does, that same code could just keep the channel around for POST channels, and replay the OnStartRequest if CTP occurs. If the networking code doesn't work that way, it will be uglier.
Blocks: e10s-plugins
Blocks: 1044769
Depends on: jsplugins-oop
No longer depends on: jsplugins-oop
Blocks: jsplugins
No longer blocks: e10s-plugins, 1044769
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.