Confirmed users
1,041
edits
Extension Manager UI: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
(Updated to project template) |
mNo edit summary |
||
| Line 15: | Line 15: | ||
** for example, we display an update now button for addons with updates within the list which allows tabbing to addons that are not displayed. This is to specifically call out that accessibility must be taken into account when designing the user interface. | ** for example, we display an update now button for addons with updates within the list which allows tabbing to addons that are not displayed. This is to specifically call out that accessibility must be taken into account when designing the user interface. | ||
* Add support for addon types that are already defined but not supported by the user interface | * Add support for addon types that are already defined but not supported by the user interface | ||
** specifically, locales and | ** specifically, locales and plug-ins were added for 1.5 though the user interface does not support displaying these types. | ||
* Ability to view a theme's status as well as description | * Ability to view a theme's status as well as description | ||
** the element used for status when viewing themes does not resize with the window unlike with extensions which prevents being able to read the complete theme's description and status message in several cases. | ** the element used for status when viewing themes does not resize with the window unlike with extensions which prevents being able to read the complete theme's description and status message in several cases. | ||
| Line 36: | Line 36: | ||
== Background == | == Background == | ||
The Extension Manager user interface has not been updated significantly to keep up with new features and functionality that has been added since its initial inception. Besides adding capabilities to be leveraged by new features / functionality there are also | The Extension Manager user interface has not been updated significantly to keep up with new features and functionality that has been added since its initial inception. Besides adding capabilities to be leveraged by new features / functionality there are also usability enhancements that should be addressed with the primary one being discoverability. | ||
== Use Cases == | == Use Cases == | ||
| Line 57: | Line 57: | ||
== Impact == | == Impact == | ||
The current design impacts the following areas of development | The current design impacts the following areas of development | ||
* Application / extension locale management (see [https://bugzilla.mozilla.org/show_bug.cgi?id=285848 bug 285848] which in turn impacts inline spell check (see [https://bugzilla.mozilla.org/show_bug.cgi?id=329668 bug 329668]) for Firefox 2.0. | * Application / extension locale management (see [https://bugzilla.mozilla.org/show_bug.cgi?id=285848 bug 285848] which in turn impacts inline spell check (see [https://bugzilla.mozilla.org/show_bug.cgi?id=329668 bug 329668]) for Firefox 2.0. | ||
* Extension Blocklisting (see [https://bugzilla.mozilla.org/show_bug.cgi?id=318338 bug 318338]). | * Extension Blocklisting (see [https://bugzilla.mozilla.org/show_bug.cgi?id=318338 bug 318338]). | ||
* Extension Dependencies (see [https://bugzilla.mozilla.org/show_bug.cgi?id=298497 bug 298497]) which in turn | * Extension Dependencies (see [https://bugzilla.mozilla.org/show_bug.cgi?id=298497 bug 298497]) which in turn impacts Application / extension locale management. | ||
=== Extensions === | === Extensions === | ||