1,071
edits
|  (New page: In trying to redesign the Firefox 3 Add-Ons Manager UI (AMUI), the team has found that it would be useful to document the various user interaction paths. It should help simplify testing an...) | No edit summary | ||
| Line 1: | Line 1: | ||
| In trying to redesign the Firefox 3 Add-Ons Manager UI (AMUI), the team has found that it would be useful to document the various user interaction paths. It should help simplify testing and uncover wacky edge cases. | In trying to redesign the Firefox 3 Add-Ons Manager UI (AMUI), the team has found that it would be useful to document the various user interaction paths. It should help simplify testing and uncover wacky edge cases. | ||
| * To Do: for each of these flows | * To Do: document for each of these flows | ||
| ** What is the UI screen flow | ** What is the UI screen flow | ||
| ** Decide where user notification is needed (and where in the UI it is provided) | ** Decide where user notification is needed (and where in the UI it is provided) | ||
| ** Include the full cycle (including the UI post restart) | |||
| ** Consider if Firefox behaves differently if the addon were a Themes or Plugin | |||
| = PATH-1: install an add-on = | = PATH-1: install an add-on = | ||
edits