Confirmed users
187
edits
User:David Regev/Ubiquitous Firefox: Difference between revisions
User:David Regev/Ubiquitous Firefox (view source)
Revision as of 23:28, 25 August 2018
, 25 August 2018→3c: Solving the ‘Too Many Tabs’ Problem: Broken link
David Regev (talk | contribs) m (Link to Concept Series guest posts) |
David Regev (talk | contribs) m (→3c: Solving the ‘Too Many Tabs’ Problem: Broken link) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<p style="text-align: center; color: | <p style="text-align: center; color: darkgreen; font-weight: bold;">This page was turned into a series of [https://blog.mozilla.org/labs/tag/david-regev/ guests posts] for Mozilla Labs.</p> | ||
__NOTOC__ | __NOTOC__ | ||
| Line 152: | Line 152: | ||
But how? Consider the specifics of the History Scroller in the mockup: | But how? Consider the specifics of the History Scroller in the mockup: | ||
[[Image:Ubiquitous Firefox – Figure 7.png|thumb|center|256px|Figure 7: Solving the ‘Too Many Tabs’ Problem ([http://www.flickr.com/photos/davidregev/5341947391 | [[Image:Ubiquitous Firefox – Figure 7.png|thumb|center|256px|Figure 7: Solving the ‘Too Many Tabs’ Problem ([http://www.flickr.com/photos/davidregev/5341947391/in/set-72157625790500322/ annotated version])]] | ||
When one traverses one of these tab trees, there is usually a predictable and liner order in which the page at each node is read. This is the depth-first order (which is arguably more efficient than a breadth-first order). Such a flow was boosted by Firefox 3.6 when spawned tabs were made to appear adjacent to their parent and in order. What if we simply collapsed the tree into a single dimension, preserving its natural reading order? This is exactly what the diagram shows. | When one traverses one of these tab trees, there is usually a predictable and liner order in which the page at each node is read. This is the depth-first order (which is arguably more efficient than a breadth-first order). Such a flow was boosted by Firefox 3.6 when spawned tabs were made to appear adjacent to their parent and in order. What if we simply collapsed the tree into a single dimension, preserving its natural reading order? This is exactly what the diagram shows. | ||