This will be short.
Already, skirmishes of opinion over Apple’s interpretation of Google Chrome‘s tabtitlebar – or the positioning of the tabs in the title bar of the browser in order to utilize screen space for webpages – have erupted on various news sites and blogs. Even on OS X, the jury over Safari 4‘s user interface design is divided; on the Windows port, most who express favor with Safari 4’s user interface design are usually users of Windows Vista, so the main supposition is that those who have the most trouble with the tabtitlebar are Windows XP users; oh, and (on a cross-platform basis) people who simply like more screen real estate for pageviewing.
Of course, Google Chrome Beta (Google’s first browser, and currently Windows-only) was the first notable web browser to publicly promote the UI infusion, and it was not without its initial criticisms for that same reason (among others, including the option of sending anonymous usage and crash data to Google). Safari 4 Beta, on the other hand, marks a first for Apple in its legendary user interface history, and may also begin a user interface trend for Apple throughout its Mac OS X applications (Finder, Mac OS’s file navigation app, is hinted to have tabs in early alphas of Snow Leopard, OS X’s 6th iteration, so it may well take up Safari 4’s tabtitlebar feature).
Many have written about problems with this emerging user interface widget, which utilizes the operating system’s window manager by embedding navigation between tabs within the title bar (mostly on Windows). Personally, I think it is a good idea due to a month or so of using Google Chrome (I also find the process-per-tab idea to be a good idea), but problems still linger with both implementations as far as I’m concerned.
- Speed: Chrome is far better in the speed department than Safari as far as opening, closing and navigating between tabs is concerned (again, maybe because of the process-per-tab idea). The Windows port of Safari 4, like its Mac port, does not allow an option (AFAIK) for using middle-click to close tabs; left-clicking to close tabs in Safari 4 on WinXP feels like chipping into brick. The responsiveness to clicking buttons to close and open tabs is horrendous on this platform.
- Tab navigation and perception: In this area, I’ll say that Firefox 2.0+, despite its own speed and resource management issues, did a better tour-de-force at tab navigation than Opera, Chrome or Safari, by allowing one to scroll through as many tabs as one may please without the tabs being scrunched up in the tab area. All the other browsers, even Chrome and Safari, continue to maintain the metaphor of the "limited tab area", with Safari 4 doing worse by maximizing the view of the tab of the current page in view at the expense of other tabs-in-waiting.
Yes, Firefox actually did something that I’ve come to appreciate (and wish that they could extend into a much wider territory of tab navigation; getting rid of the tab-specfic close button in 3.0 remains questionable, IMO).
There is room for improvement for Safari and Chrome in this combination of two user interface metaphors. In fact, there’s room for improvement for most of Apple’s software ports to Windows, but I highly doubt that Apple is willing to consider such ideas as unscrunching the tabtitlebar for tabscrolling or giving separate processes to each tab, just as how I doubt that Microsoft will do the same with IE8 or IE9.
