Firefox/Projects/TabCandy/Design/BrowserRestart: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 18: Line 18:


In this case, TabCandy should be loaded blank with no groups or tabs. There are a couple of cases we'll need to handle.
In this case, TabCandy should be loaded blank with no groups or tabs. There are a couple of cases we'll need to handle.
''If TabCandy groups are NOT integrated into Session Restore''
* If the user restores a window, that window's Tab Candy is fully restored.
* If the user restores a tab in isolation or multiple tabs it restores all of the groups that contain those tabs and none of the groups that don't. All ungrouped go where they were before.
* If the user uses the session restore feature after starting to populate TabCandy by browsing, then we try to merge the two sets of groups (i.e., restore the old groups and then let the pushAway code handle the overlaps).
''If TabCandy groups are integrated into Session Restore''


* If the user restores a window, that window's Tab Candy is fully restored.  
* If the user restores a window, that window's Tab Candy is fully restored.  
* If the user restores a tab in isolation or multiple tabs without groups, they all get put into a untitled group and placed as in the First-Run experience.
* If the user restores a tab in isolation or multiple tabs without groups, they all get put into a untitled group and placed as in the First-Run experience.
* If the user restores groups or multiple groups, just those groups are restored. And orphaned tabs are placed in an untitled group in the largest open spot.
* If the user restores groups or multiple groups, just those groups are restored. And orphaned tabs are placed in an untitled group in the largest open spot.
* If the user uses the session restore feature after starting to populate TabCandy by browsing, then we try to merge the two sets of groups (i.e., restore the old groups and then let the pushAway code handle the overlaps).
577

edits