154665 - sidebar arrow buttons interfere with adding panels

Status: RESOLVED EXPIRED

(SeaMonkey :: Sidebar, defect)

Description

[Jesse Ruderman]

Steps to reproduce:
1. Get 9-12 tabs in your sidebar.
2. Make the first eight tabs visible (the maximum you can have without getting
arrow buttons) using the Tabs dropdown.
3. Try to make the last one visible.

Result: nothing appears to happen.
Expected: arrow buttons should appear, the first tab on the sidebar should
scroll off the top, and the newly visible tab should become selected.

Similar problems occur if you start with nine visible, scroll to the top, and
add a tenth.

Adding a new panel (window.sidebar.addPanel) isn't quite as bad.  It makes the
arrow buttons appear but still doesn't scroll to and select the new panel.

Comment 1

[Robert Kaiser]

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

Comment 2

[Robert Kaiser]

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