497
edits
Perceived Performance: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* Implement the OS X scrolling model for our Windows and Linux builds of Firefox ([https://bugzilla.mozilla.org/show_bug.cgi?id=462809 bug 462809]) | * Implement the OS X scrolling model for our Windows and Linux builds of Firefox ([https://bugzilla.mozilla.org/show_bug.cgi?id=462809 bug 462809]) | ||
* Use a real time strategy game style scroll box in the content area, so you can quickly move around a page just by moving the mouse | * Use a real time strategy game style scroll box in the content area, so you can quickly move around a page just by moving the mouse | ||
* Subtle but smooth graphics accelerated back and forward animations, like a very very slight fade and pane) | |||
* Marking menu on downclick (to something on the page that doesn't take the focus) for back and forward navigation, execute the action on hover instead of upclick so that it feels extremely responsive. The user needs to hover back to center to cancel. ([http://people.mozilla.com/~faaborg/files/daf/pieNav.png mockup of the interface] ) | |||
* Increase the amount of visual change when loading a slow page, for instance transition to a large water mark style throbber that appears in the center of the content area if no information has loaded yet | * Increase the amount of visual change when loading a slow page, for instance transition to a large water mark style throbber that appears in the center of the content area if no information has loaded yet | ||
* Keep firefox running for a moment after close for the set of users who close and reopen the application in order to do a search (because the start page has a search field, and they don't know about the search bar, location bar, or home button). | * Keep firefox running for a moment after close for the set of users who close and reopen the application in order to do a search (because the start page has a search field, and they don't know about the search bar, location bar, or home button). | ||
* Use a 1 pixel pulsing progress bar at the bottom of the location bar to denote progress in addition to activity (safari 3 style, but not as heavy). | * Use a 1 pixel pulsing progress bar at the bottom of the location bar to denote progress in addition to activity (safari 3 style, but not as heavy). | ||
* Don't require the user to hit the down arrow in order to access the first result in the awesome bar (complicated, details in [https://bugzilla.mozilla.org/show_bug.cgi?id=410837 bug 410837]) | * Don't require the user to hit the down arrow in order to access the first result in the awesome bar (complicated, details in [https://bugzilla.mozilla.org/show_bug.cgi?id=410837 bug 410837]) | ||
* Give the awesome bar the focus on open so you don't have to focus it yourself before navigating to a particular location | * Give the awesome bar the focus on open so you don't have to focus it yourself before navigating to a particular location | ||