Firefox/Projects/Rebuild Software Update without browser element: Difference between revisions
Jump to navigation
Jump to search
(→Design) |
|||
| Line 11: | Line 11: | ||
= Non Goals = | = Non Goals = | ||
* major redesign of the major update offer screen | |||
* adding controls/fields to ask users why they are declining an update | |||
= Design = | = Design = | ||
Revision as of 00:52, 26 February 2009
Overview
Sprint lead: rs
Sprinters: rs, beltzner
- Description
- Instead of a page that has a browser element, change the update snippet format to include references to resources (images, text) which will be assembled in a XUL dialog on the client side.
Goals / Use Cases
- Removing the browser element will remove the requirement to verify the size of the billboard content per locale.
- Make the ui look more like it is part of the application.
Non Goals
- major redesign of the major update offer screen
- adding controls/fields to ask users why they are declining an update
Design
The updater window should look like this-ish:
with:
- a background image (stored as a data URI in the update snippet)
- a logo image (stored as a data URI in the update snippet)
- large header text (stored as text data in the update snippet)
- bold subheader text (stored as text data in the update snippet)
- description text (stored as text data in the update snippet)
Bugs
- Bug 480178 - Rebuild Software Update without browser element
- Bug 475671 - Separate the billboard url from detailsURL in the update xml