A friend of mine who works at Mozilla showed me this some time ago. While I like to see the innovation and spirit (as always with Aza's work), Here I think they

A friend of mine who works at Mozilla showed me this some time ago. While I like to see the innovation and spirit (as always with Aza's work), Here I think they overshot and made the problem somewhat more complicated than it needs to be. I don't understand why it would be considered an improvement to have to go to a different screen to manage tabs. Scanning a chessboard of icons/pics versus a bullet list seems like a small step backwards. I tend to believe that simplicity wins over prettiness. I'd love to find out if Aza has done user testing with the tree-style tab approach and what feedback he got back. There simply has to be a reason why Mozilla hasn't considered that approach. My perfect browser would do this to bridge the two worlds: * Start out with tabs across the top. * As soon as the tab count increases to make titles less than five-six characters, offer a popup that says "For managing lots of tabs, we recommend using the tab tree sidebar" and points to the button. * User presses the button and they get the behavior of the Tree Style Tab extension instead of tabs at top or it asks the same question when you start rather than waiting, so power users can put tabs on the side if needed.