2
edits
Perceived Performance: Difference between revisions
Jump to navigation
Jump to search
→Firefox startup
(→Too many tabs: add a bug reference) |
|||
| Line 11: | Line 11: | ||
* A splash screen could alleviate the issue of users not knowing whether their initial double-click to launch Firefox was successful, and inadvertently slowing down startup by making Firefox open ''two'' windows. | * A splash screen could alleviate the issue of users not knowing whether their initial double-click to launch Firefox was successful, and inadvertently slowing down startup by making Firefox open ''two'' windows. | ||
** This would only make a difference if new window time was a significant component of startup time. And anyway, it's the OSes job to indicate whether or not an application-start action was successful. (E.g. on Mac, the Dock icon bounces.) | ** This would only make a difference if new window time was a significant component of startup time. And anyway, it's the OSes job to indicate whether or not an application-start action was successful. (E.g. on Mac, the Dock icon bounces.) | ||
** An alternative to the splash screen could be to show the window itself with the size it will have, but empty, and fill it with menus and controls when they are available. Maybe even fill it gradually (ie. progressive rendering for xul). | |||
* Newly opened and currently selected tabs should have higher priority than other loading in background (from previous session). Additionally most-visited websites and nearby tabs could also have some priority boost (I'm talking about >10 or >20 open tabs scenario). | * Newly opened and currently selected tabs should have higher priority than other loading in background (from previous session). Additionally most-visited websites and nearby tabs could also have some priority boost (I'm talking about >10 or >20 open tabs scenario). | ||