Closed Bug 921916 Opened 11 years ago Closed 10 years ago

e10s support for Plugin events

Categories

(Firefox :: General, defect, P2)

Product:
Firefox
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Firefox 35
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: markh, Assigned: mconley)

References

(Blocks 1 open bug)

Details

+++ This bug was initially created as a clone of Bug #918663 +++

Plugin events (eg, PluginBindingAttached, PluginCrashed, PluginNotFound, etc) fired in the content process don't make their way to the parent process where they are handled - eg, see browser-plugins.js
Blocks: e10s-plugins
No longer blocks: e10s-m1
Assignee: nobody → mconley
Status: NEW → ASSIGNED
I've started by auditing what gPluginHandler does so I can determine which events need to bubble up, and which events need to be handled from within the content process (if any).
Hm - a quick peek at bug 899347 makes me think that this will get fixed by that.

Re-adjusting estimate. I like freebies.
Depends on: 899347
Status: ASSIGNED → NEW
Priority: -- → P2
This was fixed by bug 899347.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 35
You need to log in before you can comment on or make changes to this bug.