Perceived Performance: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 9: Line 9:
* 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
* Quickly load pages out of cache and then fade to a copy loaded off of the network once it is ready (also, display a greyed out version of the cache page with highlighted form fields when prompting the user if they want to ressend information)
* Extend the password manager to allow for automatic log ins (with feedback that this is happening)
* Load the frontmost tab on startup before the others (filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=496458 bug 496458])
* Load the frontmost tab on startup before the others (filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=496458 bug 496458])
* Don't show the progress spinner for the address bar until 200-300ms have passed (it currently appears instantly, and makes it feel like you're waiting for results).
* Don't show the progress spinner for the address bar until 200-300ms have passed (it currently appears instantly, and makes it feel like you're waiting for results).
497

edits