Sidebar navigation buttons remain visible when sidebar removed/minimized.

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: home, Unassigned)

Tracking

(Depends on: 1 bug)

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Sidebar 'tab-up' and 'tab-down' buttons remain visible after sidebar is hidden
or removed. Always reproducible (3/4-pane view with folders and sidebar sharing
the far left pane, messages and message view sharing righthand pane):

1) Open the sidebar.
2) minimise the sidebar using arrows on divider between folders window and
sidebar. Note that tab up/down buttons still visible.

Also:
3) Hit F9 (or click View-> Sidebar) to remove sidebar. Sidebar disappears, but
buttons remain.

Closing the mail window and reopening removes the excess buttons if the sidebar
has been removed (they still remain if the sidebar has just been minimised).

Updated

17 years ago
QA Contact: esther → olgam

Comment 1

17 years ago
I don't get it - how 'tab up/down buttons still visible' after sidebar is hidden
or removed. I tried and don't see the problem. May be screen-shot will help?

Comment 2

17 years ago
I see it on 3-pane window.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 3

17 years ago
Created attachment 75364 [details]
Image of sidebar buttons when sidebar closed.

Here's a screenshot of the bug (bottom left corner of Mail window). I can
supply a full screenshot if that would be helpful. Note I tried this at home
and could'nt reproduce the bug - my guess is that you need a large number (I
have 10 at work) of sidebar tabs for the problem to appear.

Comment 4

17 years ago
Also after clicking a few times on grippy we can get the state that Sidebar does
not return to the previous  state - only upper part of Sidebar is shown. This
part seems related to bug 132423.

Updated

15 years ago
Depends on: 178003
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: olgam → message-display

Comment 5

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 6

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.