Confirmed users
933
edits
Improved missing plugin experience: Difference between revisions
Improved missing plugin experience (view source)
Revision as of 04:02, 9 February 2012
, 9 February 2012{{bug|264254}}
(add bug 678707) |
({{bug|264254}}) |
||
| Line 22: | Line 22: | ||
* We should never imply that installing a plugin is absolutely necessary for the browser to function (like we kind of do today), but rather that plugins are required for certain types of content | * We should never imply that installing a plugin is absolutely necessary for the browser to function (like we kind of do today), but rather that plugins are required for certain types of content | ||
* {{bug|678707}} - We should label which plugins you'll end up downloading/installing in the location where we show the "Missing Plugin" message. Right now, you don't know until you go ahead and start the process | * {{bug|678707}} - We should label which plugins you'll end up downloading/installing in the location where we show the "Missing Plugin" message. Right now, you don't know until you go ahead and start the process | ||
* We want to stop using Plugin Finder Service, and instead hardcode the small list of plugins we care about to simplify the code and maintenance burden | * {{bug|264254}} (essentially WONTFIX) - We want to stop using Plugin Finder Service, and instead hardcode the small list of plugins we care about to simplify the code and maintenance burden | ||
** We are maintaining plugin data for plugincheck anyways | ** We are maintaining plugin data for plugincheck anyways | ||
}} | }} | ||