Customize Sidebar: Still able to "remove" a tab, even when panel not active.

RESOLVED EXPIRED

Status

SeaMonkey
Sidebar
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Jay Farrell, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
After adding a new tab (Stocks) using "Customize Sidebar", I see the tab placed 
on the right hand panel "Tabs in Sidebar". At this point the tab is highlight 
blue and the "remove" button becomes active. If I then click on another tab in 
the left window (sports), "sports" becomes highlighted blue, and "stocks" is 
greyed-out. Remove is still active (even though "stocks" is greyed out) and 
when I click on it, it removes "stocks" from my "tabs in sidebar".

I think that when I click on "sports", the hightlight for "stocks" should be 
removed and the "remove" button should be greyed out again.
*** Bug 145694 has been marked as a duplicate of this bug. ***

Updated

16 years ago
Target Milestone: --- → mozilla1.1alpha

Comment 2

15 years ago
Something I noticed while looking at this (in Moz 1.1b) was that selecting a tab
from the right list (Tabs in Sidebar) *does* remove the selection on the left
list (Available Tabs) and grays-out the Add and Preview buttons. This is an odd
inconsistancy, and I'd like to see anyone rationalise it. It also looks like a
fix would be a simple JavaScript 2-line change, too.

Comment 3

14 years ago
retargeting
Target Milestone: mozilla1.1alpha → Future
Product: Browser → Seamonkey
Assignee: samir_bugzilla → nobody
QA Contact: sujay → sidebar
Target Milestone: Future → ---

Comment 4

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 5

8 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.