User:David Regev/Ubiquitous Firefox: Difference between revisions

m
Line 142: Line 142:
* The tab on top, no longer a proxy for an individual page but a container for a chronological sequence of pages, displays the favicons of the current page and the two surrounding pages. The tab is now a reminder not only of the site being viewed within it but of the context as well.
* The tab on top, no longer a proxy for an individual page but a container for a chronological sequence of pages, displays the favicons of the current page and the two surrounding pages. The tab is now a reminder not only of the site being viewed within it but of the context as well.


Much of this interaction model was inspired by Bret Victor’s [http://worrydream.com/Scrolltabs/ Scrolltabs] demo, which was proposed as a solution to the ‘too many tabs’ problem. The way tabs display three favicons instead of a page title will allow tabs to take up less space on the tab bar and will, therefore, free up space for more tabs. This extra space, however, will not be needed as much, as the next step will dramatically decrease the need for too many tabs in the first place. The final interaction aspect of the History Scroller will present its own solution to the ‘too many tabs’ problem.
Much of this interaction model was inspired by Bret Victor’s [http://worrydream.com/Scrolltabs/ Scrolltabs] demo, which was proposed as a different solution to the ‘too many tabs’ problem. The way tabs display three favicons instead of a page title will allow tabs to take up less space on the tab bar and will, therefore, free up space for more tabs. This extra space, however, will not be needed as much, as the next step will dramatically decrease the need for too many tabs in the first place. The final interaction aspect of the History Scroller will present its own solution to the ‘too many tabs’ problem.


=== Step 3c: Solving the ‘Too Many Tabs’ Problem ===
=== Step 3c: Solving the ‘Too Many Tabs’ Problem ===
Confirmed users
187

edits