Improve the "Plug-in Finder" Experience
Detailed Description
This item pertains to the behavior of the "default plug-in" that gets used for <embed> tags for which no plug-in can be found. Gecko/embedding plans to enhance that default plugin with support that will automatically download and install a number of popular plugins. That will be accomplished by tying into support provided by servers at netscape.com (or somewhere else in aol.com).
That feature will not require any "front end" work aside from the UI that the default-plugin/plugin-finder-plugin provides.
There is one bit of related "front end" work that needs to be done: Tie into that same service when appropriate content types are encountered elsewhere. That is, in contexts aside from use with <embed> or <object> tags. For example, this will apply in cases where the user clicks on a link to a stand-alone Acrobat file.
This triggers display of the "unknown content" dialog (aka "helper app launcher dialog") where we currently offer the option to launch an already installed application, or to save the content locally. We need to add a third option: to find a plug-in that can handle the content.
Choosing that option would then trigger the same thing that happens when such content is encountered within a "plugin" (<embed> tag).
Tasks
- Add third option to "helper app launcher" dialog: "Look for Plug-in." 1 day
- Add code to nsHelperAppDialog.js to implement that option. This will be done via calling into code shared with, and already in place in, the default plugin. 3 days