Closed Bug 1092119 (jsplugins) Opened 10 years ago Closed 6 years ago

Js Plugins tracking bug

Categories

(Core Graveyard :: Plug-ins, enhancement)

enhancement
Not set
normal

Tracking

(e10s-)

RESOLVED INCOMPLETE
Tracking Status
e10s - ---

People

(Reporter: jimm, Unassigned)

References

Details

(Keywords: meta)

Tracking bug for js-plugin work.
Alias: js-plugins
Alias: js-plugins → jsplugins
No longer blocks: jsplugins-oop
Depends on: jsplugins-oop
Depends on: 1044769
Depends on: jsplugins-streams
Depends on: jsplugins-params
Blocks: e10s-plugins
tracking-e10s: --- → -
Depends on: shumway-m4
Whiteboard: [shumway:fb2]
No longer blocks: e10s-plugins
Make bugs with "[shumway-fb2]" whiteboard tag block shumway-fb2 meta bug 1110300.
Blocks: shumway-fb2
Blocks: shumway-fb1
No longer blocks: shumway-fb2
Whiteboard: [shumway:fb2]
Blocks: shumway-jw1
No longer depends on: shumway-m4
Blocks: shumway-jw2
No longer blocks: shumway-fb1, shumway-jw1
This jsplugins meta bug does not need to block Shumway milestones (though some jsplugins implementation bugs will).
No longer blocks: shumway-m3, 1111507, shumway-jw2
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
(In reply to Rob Wu [:robwu] from bug 1457500 comment #3)
> (In reply to ExE Boss from bug 1457500 comment #2)
> > Will this be implemented in a way that would allow for WebExtensions to act
> > as plugins (like what I outlined in bug 1451983)?
> 
> Yes. The extension should be able to handle content, regardless of whether
> they are directly loaded in a tab, or embedded through <embed>, <object>,
> <frame> or <iframe>.
See Also: → 1457500
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.