Confirmed users, Bureaucrats and Sysops emeriti
2,974
edits
Awesome Bar v2: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
(Created page with "{{FeatureStatus |Feature name=Awesome Bar v2 |Feature stage=Definition |Feature health=OK |Feature status note=Product team defining the requirements for this feature. }} {{Featu...") |
mNo edit summary |
||
| Line 8: | Line 8: | ||
|Feature product manager=Asa Dotzler | |Feature product manager=Asa Dotzler | ||
}} | }} | ||
{{FeaturePageBody}} | {{FeaturePageBody | ||
|Feature overview=The Awesomebar is one of the stand-out features of Firefox. We should revisit our algorithms and styling to ensure that users are getting the most from it. In addition, we should make sure that the combination of the inline auto-complete and the Awesomebar pop-up works as well as it can for our users. | |||
User surfing patterns, bookmarking habits, etc. have changed significantly over the last few years. More users are spending more time on fewer sites than ever before. Are we optimized for the user who spends most of her time on Facebook or Twitter? Does our algorithm respond to the changing structure of URLs on the web -- like the increasing usage of hash bang URLs? | |||
I know these are questions and not answers so I'll be working with folks to come up with answers that will become the functional and design specs for this feature. | |||
}} | |||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority=Unprioritized | |Feature priority=Unprioritized | ||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus}} | ||