No, it's still there. You simply have to turn it on in the preferences. :-)
On Mar 1, 2:53 pm, Evan <[email protected]> wrote: > I agree with this as well. > > One other thing I wanted to add, was that, as a PC user, the only > reason I ever used Safari 3, is because it was the only way in Windows > to get those gorgeous, Apple anti-aliased fonts. > > Safari 4 took this option away (at least for now). > > Has the Chrome team ever considered this as a possibility? Improving > the visual appearance of webpages... Or would it be too much of a > resource hog? > > On Mar 1, 8:36 am, Jarrett Wold <[email protected]> wrote: > > > > > This sums up my opinion on the matter nicely, good article and I agree > > with it. > > > Full Article: http://osnews.com/story/21056/Safari_4_Beta_UI_Disaster > > > "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. > > When Google pushed out Chrome, it had the tabs in a different place > > than most other browsers. Wait, let me correct that - it had the > > browser controls in a different place. Instead of the browser controls > > being located atop the tabs, they were placed inside the tab. The > > result was that each web page had its own set of controls. The > > difference between "moving the tabs" and "moving the browser controls" > > may seem arbitrary, but as it turns out, it seems to explain perfecty > > well why Safari 4 is such a UI disaster. > > > You see, everybody on the web focussed on the tabs in Chrome being > > part of the titlebar, while in fact, they are not. When you run a > > Chrome window in a non-maximised state, the tabs are actually > > underneath the titlebar; only when you maximise a Chrome window do > > they appear to be part of the titlebar. I specifically say "appear", > > because the tabs are actually an overlay. > > > In Chrome, the browser controls have become part of the web page, > > which from a web application perspective makes perfect sense: the > > browser buttons and address bar, in essence, are part of the web > > application. In other words, each tab in Chrome is an "application", > > one stacked atop another. In any case, there is a clear distinction > > between the titlebar and tabs, not only functionally, but also > > visually. The titlebar and window frame in Chrome are Aero Glass, > > while the tabs are content-coloured. This makes the distinction > > between the two perfectly crystal clear." --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
