Why shouldn’t there be any configuration for this? I personally think it would be very very awesome if this new tab iteration was made up of modules that can be added and rearraged. Something like a toolbar: drag and drop controls into it and rearrange. I chose FF because of the extensive customization available to do whatever I want, and I don’t think you should compromise on that. At the very least, let me pin websites.

I would’ve thought that it make more sense that the titles of the websites were below or above the thumbnail, not to the left.

I know all these new things can add weight to the iteration and make it load slower, but a button, a search bar and a few thumbnails is far too little IMHO. And I really don’t think you should compromise on customizability; that’s what FF is all about. Hope all my suggestions helped =)

I guess that the reopen action should stay because it is more discoverable than the menu item “History” -> “Recently closed tabs”.

I agree with Ami: a very common use case is when you want to open a tab with the same history as an existing tab. It is probably more common than searching for a word in a new tab. IE solves this problem elegantly; I think I would prefer that to the proposed design.

As a compromise, the previous tab’s content can be one of the context items shown in the new tab, and when it is opened it can contain the history of the old tab.

If you have context-sensitive content, it should be according to the text selected before opening the new tab, as well as the text typed in the Awesome Bar. As you type in the Awesome Bar, the results should replace the initial contents of the window. (The downside of this is when you want to see a long list of pages matching your Awesome Bar query but want a small window.) They should appear after some delay to avoid slowing down your typing.

I updated today from 0.18 (I think) to 0.21 or whatever this is (I forget), and the wonderful about:tab is now completely broken! You had it right with the smaller thumbnails down the right side with the RSS feeds… this new design with either the text list or the 4 large left-aligned thumbnails is uglier, slower, and … wacker.

My biggest problem though, a MUST FIX NOW problem: Now when I create a new tab, “chrome://abouttab/content/tab.html” sits in the location bar with the cursor at the end of it, messing up whatever I was about to type in the AwesomeBar.

I’m about to uninstall this, you guys can let me know when you get it fixed.

1) Prevent overlapping: A long undo-close-tab-box flows into the feed items for the top-most page. (seen after closing http://www.dpreview.com/)

2) Page title detection: something is wrong with hgweb pages, it shows titles “comm” and “mozilla” for e.g. “comm-central: pushloghtml”

3) You’ll probably need to have selectable feeds. Again http://www.dpreview.com/ is a good example, it has three completely different feeds, and Ambient News always picked the wrong (as in “not main content”) one. And about:tab inherited that issue.

4) Be quicker, hitting Ctrl-T and quickly typing is interfered after a couple of characters, as focus is stolen. Same for Bookmarks sidebar, focus is stolen when I hit Ctrl-T, Ctrl-B and type quickly in the sidebar search box.

5) Mentioned by robcee elsewhere: the tab page shouldn’t appear in the tab’s history. When something is loaded in the tab to replace the NewTab page, the Back-button should be still disabled.

Good start, now looking forward for more!

Put search and undo closed tab along the top of the window.

Then have two rows with three Frecently visited sites in each. Make plenty of space above them though so it isn’t all one big mess.

Stick with the idea of greyscale or perhaps 70% desaturated (30% saturated) thumbnails.