Confirmed users, Bureaucrats and Sysops emeriti
2,974
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 19:42, 29 July 2011
, 29 July 2011no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 8: | Line 8: | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Asa Dotzler | |||
|Feature feature manager=Blair McBride | |Feature feature manager=Blair McBride | ||
|Feature lead engineer=Blair McBride | |Feature lead engineer=Blair McBride | ||
| Line 17: | Line 18: | ||
|Feature users and use cases=Quoting from [http://blog.stephenhorlander.com/2010/06/in-content-ui-visual-unification/ shorlander's blog post]: | |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." | "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." | ||
This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.) | |||
|Feature requirements=Relevant in-content UI is able to use the shared resources to look consistent with other in-content UI. | |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 non-goals=* Implement other UI as in-content UI, such as preferences (long-term goal, separate project) | ||