Linked by Thom Holwerda on Sat 28th Feb 2009 11:47 UTC
A few days ago, Apple surprised everyone by releasing the first beta of Safari 4, the company's latest version of their WebKit browser. While I generally love Safari on the Mac (my browser of choice on that side of the fence), I've never felt as comfortable with it on the Windows side of things. In any case, this latest beta has made a very bold move in the interface department, and I'm sad to say that it's not for the better. Let me explain where it went wrong for Apple.
Permalink for comment 351809
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
However, I wish that Firefox's unscrunching of tabs for tabscrolling made it into Chrome's or Safari's tabtitlebars. That could've been a major saving grace for Safari 4, instead of maximizing the current page's tab at the expense of the other tabs within an already tight space.
...
Now, I don't think the tab behaviour of new Safari is perfect (that would be for me somewhere between Chrome and Opera), but...gods, please no, let us all forget the abomination that is FF tabbar; it works only for dozen tabs or so, if you're used to much more than that (than again...FF resource usage doesn't really allow this) you're totally lost when it comes to relation between tabs/where in them you are at the moment. They even managed to break list view of tabs - you're expected to wait for it to scroll! (vs. Start menu-like behaviour (minus hiding of course) in Opera, which also has nice tree view in the sidebar and "hold RMB & scroll" view)