Hyatt Discusses Tabs
Llywelyn writes "Über Geek David Hyatt (who, among other browser projects, works on Safari) has posted an interesting discussion about tabs, what he prefers, what works, and what doesn't."
← Back to Stories (view on slashdot.org)
...Help the flow of a web application.
Many applications involve the user going through a set of steps, and tabs can help the user understand where he is in the process, and allow him to skip forward or jump backwards if necessary. I think tabs are generally accepted in most applications nowadays as way of controlling and guiding program flow.
What is more of a debate where I work is if pagination is better than scrolling.
(I vote scrolling for CTRl+F purposes)
"I only speak the truth"
Karma: null(Mostly affected by an unassigned variable)
I think he really has hit the nail on the head. Tabs aren't for everyone, but its stupid for someone building a browser to not implement them. If I were to hypothetically speaking gotten my hands on v64 build of Safari, I would hypothetically know that tabs are being implemented like Dave describes. I've already adopted Safari as my primary browser, non of its current deficiencies are so glaring that any other browser is better for me overall.
It is nice to see competition in the browser world, cause in the end its the user who wins.
Is it really necessary on /. to qualify anyone as an übergeek?
I use netscape 7 at work, and have multiple instances running with multiple tabs open for each for my api references. I usually have one instance for all my opened Oracle doc pages, and another for Java. I just keep them open and tab between document. Very handy.
SCO to Hell
Well, one could reduce the annoyance by only asking in case there's more than one tab open.
Even better idea: What if cou could undo that accidental close? Maybe the browser, after getting in a "close-ready" state (appearing already closed), would wait, say, 3 seconds before actually terminating, and if during that time you start a new one (which is a sign that you closed it accidentally), it offers you to recover that old state.
This probably should be made an option (some people might mot like the program to still hold ressources 3 seconds after it's apparent close), but I think it would be an useful one. One could also enable customizing the time to wait before really terminating.
The Tao of math: The numbers you can count are not the real numbers.
I have to disagree with David Hyatt's opinion about close boxes in tabs. I've used Galeon, and I hate having the close boxes in the individual tabs; a close box in a tab takes up such a large proportion of space that it is very easy to accidentally close a tab just by clicking on it. This happened to me so often that I stopped using Galeon and started using Mozilla.
I suppose having one close box on the right-hand side is conceptually inconsistent, but I find the Mozilla solution to be more usable. It never confused me: Mozilla's "close tab" button on the right balances with the "new tab" button on the left. I hope that Hyatt and Apple, before deciding on a solution for Chimera, do usability research with users and don't rely solely on theories of consistency.
1. Middle-click on each interesting entry
Instead, the Microsoft way is:
1. Right-click interesting entry
2. choose "open in new window"
3. Go back to main window
This takes not only Much longer, but is also very awkard because you can't organize your windows. I have every Google-search in a different window, while you would end up with 20 different windows from different searches.
Or click through all interesting links and wait everytime for the page to load.
Once you really understand what tabs can do for you, you will never go back.
Now that Microsoft has cornered the browser market, they see no more reason to innovate, er, spend more money, on the product.
When they were playing catch-up, it was all about new features. How many features have been added to IE lately?
At this point, the only changes to IE are going to be things which will make Microsoft money, like DRM.