Since Bug 312896 doubleclicking on the tabbox does not create a new tab anymore when using this userChrome.css: .tabbrowser-tabs > hbox { display: block !important; } .tabbrowser-tabs tab { min-width: 14% !important; .tabbrowser-tabs > hbox { overflow: visible !important; } Both on trunk and branch.

(In reply to comment #0) > Since Bug 312896 doubleclicking on the tabbox does not create a new tab anymore > when using this userChrome.css: I have a hard time believing that unsupported userChome hacks being broken should be considered a bug in Firefox. People using userChrome to change how the browser works in such a dramatic way should expect breakage. Surely you're not suggesting reverting that fix? That being said, it would be great if you could come up with a modification that allows your use case to work - without affecting by far the most common use case.

multirow isn't supported, we will have a better overflow solution for Fx2

Just doing my duty; reporting a bug... but sure I'm not really sad that I can't use the doubleclick function anymore. Had not even noticed it since nearly a month. And only because I was testing tab functions. But it's very difficult to say what function should be considered as most important for other people.

This bug does not exist anymore since the code does nothing anymore :( Replaced by tab scrolling.