Spun off from: <http://bugzilla.mozilla.org/show_bug.cgi?id=126095#c7> Marlon, Please advise on a short range (Mach V) design solution and consider the same for a long range solution (the sidebar redesign spec). Thanks.

6 or 7 should be the default setting, for both performance reasons and minimum system screen constraints. Is there any way we could have a splitter on the bottommost "reflow tab" which would allow users with larger screens to resize the viewable sidebar area? Or, is there a way we could detect the users screen resolution and determine that if they are 1024x768 or higher, then show more tabs?

How about detect the window size instead of screen resolution? What if I have my resolution set at 1024x768 but a small window...then the tabs would get crammed. Hmm I just though what if they resize the window. Wouldn't want to have to recalculate the number of tabs with each resize, but still wouldn't want to cram in too many tabs to a small window on a big screen.

What's wrong with recalculating the number of tabs based on a minimum tab width of so many ems or pixels? If the user has enabled opaque resize (i.e. "show window contents while dragging"), then recalculating on every resize event could pose a performance problem, but can't we work around that with timers?

retargeting

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420