I don't think the tabs make more sense up there, because that's where the title bar goes. If they reverted, though, I think I'd be a bit disappointed.

I don't have many bookmarks (they're all on Delicious), but I agree that they belong above history items.

Not sure why, but after forcing myself to stick with the new tabs, I kinda like them.

I don't. I still hate them. I wonder if you aren't confusing "getting used to them" with "kinda like them."

Mike said on March 8, 2009:

The new autocomplete is much, much better.

I still think bookmarks need to be placed above history items.

The resizer being used to move and separate tabs still confuses me - I wish they'd come up with another icon for that.

Top Sites is distracting and pretty useless. It's difficult to put a site in there unless it suggests it for you. At least about:blank still works.

I used Cover Flow for history yesterday - that was incredibly useful. Much more than I thought it would be.

The new autocomplete is much, much better. It needs to keep a URL's focus when moving the mouse away from the current selection, though.

Erik - how do you use a progress bar to load an indefinite amount of data?

The sizes of things are rarely indefinite. Your AJAX example occurs after pages load - the page can be responsible for its own "wait" timers then. If nothing else, there's almost always a counter.

Ken said on March 4, 2009:

I'm not sure if I like the spinner either but I think a "hey, I'm doing something" or "hey, I was told to fetch something" is a heck of a lot better than "I'm loading something, now I'm done, oh wait.. not really... oh yes, now I am... uh, sorry, but not really".

I've never seen that behavior at all. I've written sites that use AJAX and haven't had that problem, either. The progress bar in 3 wasn't perfect, but it was better than a completely indeterminate spinner.

Back in Web 1.0 your browser would request a page and the web server would respond with a header with the content size. This was easy to use and determine how much of something was downloaded.

Now with the wonderful Web 2.0 and sites using AJAX to download all sorts of information from a javascript... How can the browser now know how much of the page is loaded? Or even when all requests are sent and received?

I'm not sure if I like the spinner either but I think a "hey, I'm doing something" or "hey, I was told to fetch something" is a heck of a lot better than "I'm loading something, now I'm done, oh wait.. not really... oh yes, now I am... uh, sorry, but not really".

0.02

If we were talking about Safari on the iPhone, then yes, it would be a significant improvement. On a desktop system, not at all.

Having the tabs up top were a bit weird for the first day, but now like it, I think its a good saving of screen real estate.

Time to try those hidden settings...

Regarding using the status bar to drag -- yeah, you're right, that's more backwards than anybody should have to bend. It blows away the consistency of experience that we always tout on the Mac. Why not let everybody create their own crazy window controls? Agreed on the other point too -- progress should be indicated in the natural place, and besides the status bar is optional. If they wanted so badly to save the 20 vertical pixels, they could have gotten rid of the status bar and put *its* stuff in the title bar. (Not advocating that, just saying.)