Features/Firefox/In-content UI Visual Unification: Difference between revisions
Jump to navigation
Jump to search
(Created page with "{| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bold; backgro...") |
|||
| Line 42: | Line 42: | ||
== Related Bugs & Dependencies == | == Related Bugs & Dependencies == | ||
* {{bug|658431}} - Move generic page styling into separate stylesheet for reuse in other in-content UIs | * {{bug|658431}} - Move generic page styling into separate stylesheet for reuse in other in-content UIs | ||
* {{bug|658530}} - Update about:permissions style to use common in-content page styles | |||
== Risks == | == Risks == | ||
Revision as of 14:35, 20 May 2011
| Feature | Status | ETA | Owner |
| Features/Firefox/In-content_UI_Visual_Unification | Planning done, implementation starting | Firefox 7 | Blair McBride |
Summary
Do preparation work for having new in-content UI have a consistent and unified visual appearance.
Team
Who's working on this?
- Feature Manager: Blair McBride
- Lead Developer: Blair McBride
- QA: Henrik Skupin
- UX: Jennifer Boriss
Release Requirements
Relevant in-content UI is able to use the shared resources to look consistent with other in-content UI.
Next Steps & Open Issues
- Basic visual look
- Split out relevant styles from addons manager themes
- Adapt about:permissions to use new shared styles
- Breadcrumbs
- Implement breadcrumbs in a way they can be used in any in-content page
- Integrate into about:addons
- Integrate into about:permissions
- Investigate which other existing pages should have a breadcrumb trail, and integrate into those
- Should error pages have a breadcrumb trail?
Related Bugs & Dependencies
- bug 658431 - Move generic page styling into separate stylesheet for reuse in other in-content UIs
- bug 658530 - Update about:permissions style to use common in-content page styles
Risks
TBA.
Use Cases
TBA.
Designs
Test Plans
Breadcrumb trail should be fully testable via browser-mochitests. Visual styling can't be automatically tested, unless we get UI reftests.
Goals
Quoting from shorlander's blog post:
The goal is to create something that looks appealing, connects the variety of different types of UI, is recognizably in-content UI and can be styled per platform.
Non-Goals
- Implement other UI as in-content UI, such as preferences (long-term goal, separate project)