canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Features/Firefox/In-content UI Visual Unification: Difference between revisions
Jump to navigation
Jump to search
m
Features/Firefox/In-content UI Visual Unification (view source)
Revision as of 20:57, 8 July 2011
, 8 July 2011no edit summary
m (clearing in prep for migration to new feature page format (will be done momentarily)) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=In-content UI Visual Unification | |||
|Feature stage=Development | |||
|Feature status=In progress | |||
|Feature version=Firefox 7 | |||
|Feature health=OK | |||
|Feature status note=Planning done, implementation starting. | |||
}} | |||
{{FeatureTeam | |||
|Feature feature manager=Blair McBride | |||
|Feature lead engineer=Blair McBride | |||
|Feature qa lead=Henrik Skupin | |||
|Feature ux lead=Jennifer Boriss | |||
}} | |||
{{FeaturePageBody | |||
|Feature overview=Do preparation work for having new in-content UI have a consistent and unified visual appearance. | |||
|Feature users and use cases=Quoting from [http://blog.stephenhorlander.com/2010/06/in-content-ui-visual-unification/ 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." | |||
|Feature requirements=Relevant in-content UI is able to use the shared resources to look consistent with other in-content UI. | |||
|Feature non-goals=* Implement other UI as in-content UI, such as preferences (long-term goal, separate project) | |||
|Feature ux design=* [http://stephenhorlander.com/pages/incontent-ui-mockups/incontent-ui-mockups.html General in-content mockups] | |||
* [http://blog.stephenhorlander.com/2010/06/in-content-ui-visual-unification/ Blog post on in-content UI visual unification] | |||
* [http://www.cl.ly/3s0F1W2U3m37083d121M Breadcrumb trail mockup] | |||
|Feature qa review=Breadcrumb trail should be fully testable via browser-mochitests. Visual styling can't be automatically tested, unless we get UI reftests. | |||
|Feature implementation notes===== Related Bugs ==== | |||
* {{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 | |||
* {{bug|660726}} - Implement breadcrumb trail for 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? | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=P3 | |||
|Feature roadmap=Firefox Desktop | |||
|Feature list=Desktop | |||
|Feature engineering team=Desktop front-end | |||
}} | |||
{{FeatureTeamStatus | |||
|Feature products status=tbd | |||
|Feature engineering status=tbd | |||
|Feature security status=tbd | |||
|Feature privacy status=tbd | |||
|Feature localization status=tbd | |||
|Feature accessibility status=tbd | |||
|Feature qa status=tbd | |||
|Feature ux status=tbd | |||
}} | |||