The tab overlow implementation allows users to move up or down only one tab at a time when the number of ``included'' tabs in a profile exceeds the sidebar.num_tabs_in_view pref for the same profile. We need a way for users to get to the tab of their choice with less clicks and more ``smmothness'' or continuity. This is a usability defect. The prescribed solution per UI design, engineering etc. is to navigate normally till the selected tab hits a boundary, then close the selected tab and bring in as many as will fit. We should also disable the navigation buttons (icon change should suffice) when a bound is hit and there are no more tabs above when we were moving up or no more tabs below when were moving down.

This is a dup of bug 126559

Nope, not a dupe; this is a short-term usability improvement for the current implementation.

nsbeta1+ per Nav triage team

*** Bug 129904 has been marked as a duplicate of this bug. ***

we need to also fix the following case: after deleting tab from customize sidebar, we are not showing an open tab in the sidebar. So for example, if you have Search tab open in sidebar and you have bookmark tab below it(closed). Then yo go into Customize Sidebar and delete Search, then click OK on Customize Sidebar. Then Bookmark tab in sidebar should be the active tab in the open state.

Yes, thanks for noting this. I believe this is the dependent bug 128692.

here is a screen shot of the mac classic sidebar "overflow" arrows. They appear white and not the grey chrome color that the rest of the sidebar has.

-> caillon

Nav triage team: nsbeta1-

->Back to you samir.

Probably easiest solved by doing bug 139855: replace the tabs by a single dropdown box.

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

Still valid.