Stop shipping the Default Plugin on 1.9.2; ship pluginGlue.js instead and turn it on

RESOLVED FIXED

Status

RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: alqahira, Assigned: alqahira)

Tracking

1.9.2 Branch
All
Mac OS X

Details

(URL)

Attachments

(1 attachment)

Created attachment 441660 [details] [diff] [review]
bye-bye DefaultPlugin, hello similarly non-functional pluginGlue.js!

As detailed somewhere else and in bug 316593 comment 7, the 1.9.2 Default Plugin no longer offers plug-in finding services.

While there is no embedding-friendly working solution for plug-in finding, we can ship a 4K JS component instead of a 68K plug-in and get the same (non-plug-in-finding) experience on 1.9.2, with slightly prettier UI.

And, while DP will almost assuredly never be "fixed" to offer plug-in finding again, there's a chance we can come up with something usable in bug 316593 to actually find plug-ins.  Further, even though the post-Lorentz in-content UI is really ugly, it's still far prettier than that provided by the DP (and is hackable).
Attachment #441660 - Flags: superreview?(stuart.morgan+bugzilla)

Comment 1

9 years ago
Comment on attachment 441660 [details] [diff] [review]
bye-bye DefaultPlugin, hello similarly non-functional pluginGlue.js!

Can't argue with that; sr=smorgan

Just think, in 1.9.3 maybe the whole step can go away :)
Attachment #441660 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
http://hg.mozilla.org/camino/rev/d4265d00e928
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.