I feel like people are using tabs as a replacement for a good history system. At least in all current browser implementations, tabs are "running". Even if we can make the UI scale to 1000 tabs, the 500 flash instances that are likely running aren't really going to perform. The making tab performance scale is a separate technical issue that will hopefully also improve.
Looking at a lot of these design videos, they looked more like good ideas to me for history navigation than tab navigation. If history was good, I think people wouldn't be so worried about "losing something" by closing a tab. Having had bad history systems for so many years, people are now trained to keep tabs open if they ever might want to look at that page again in the future :\ On Sat, Jul 18, 2009 at 1:16 AM, Peter Kasting<[email protected]> wrote: > http://design-challenge.mozilla.com/summer09/ > The results of the "Reinventing Tabs in the Browser" challenge have been > announced. > "Collapsible Tab Groups" includes among others some things I've proposed, > including grouping and collapsing groups. > "Favitabs" reminds me of some old brainstorming ideas from pamg about > converting certain tabs into favicon buttons. > Folks considering the future of tabs (e.g. Ben, Glen, Scott) might do well > to take a look at some of these. > PK > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
