Linked by Thom Holwerda on Sat 28th Feb 2009 11:47 UTC
Apple 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.
Thread beginning with comment 351146
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Not that bad
by google_ninja on Sun 1st Mar 2009 01:42 UTC in reply to "Not that bad"
google_ninja
Member since:
2006-02-05

Tabs on top do make sense. The google implementation is the best tab implementation I have seen in any program ever. Apple's implementation sucks compared to it.

That being said, I would use safari 4 over firefox any day, but it is a shame that right on the heels of someone doing the same thing so right, it got copied so poorly.

Reply Parent Score: 4

RE[2]: Not that bad
by raynevandunem on Sun 1st Mar 2009 02:18 in reply to "RE: Not that bad"
raynevandunem Member since:
2006-11-24

I concur; Safari 4's tabtitlebar doesn't look or work too good on WinXP (it looks better on Vista and best on OS X, as far as I've seen from photos), while Chrome works well on that same platform.

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.

The tabtitlebar is not the disaster in Safari 4, just how Apple makes it work.

Reply Parent Score: 2

RE[3]: Not that bad
by zima on Thu 5th Mar 2009 14:26 in reply to "RE[2]: Not that bad"
zima 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)

Reply Parent Score: 1