142258 - IMAP Shared UI: Shared Folders incons do not display for OTHER USER'S Shared Folders

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Karen Huang]

Used 05-03-08-1.0.0 branch build

IMAP Shared Folders incons do not display for OTHER USER'S Shared Folders

Now, IMAP Shaed Folder icons are only displaying on PERSONAL Shared Folders, but 
are NOT displaying for OTHER USER'S Shared Folders.

1)Setup two accounts for IMAP Shared Folders 
2)Login to PERSONAL account.
3)View that Shared Folders icons are displaying on this PERSONAL IMAP account.
4)Login to OTHER USER'S account.

Actual Results: View that Shared Folders icons are NOT displaying on OTHER 
USER'S account.

Expected Results: IMAP Shared Folders icons should also display on OTHER USER'S 
account.

Comment 1

[Karen Huang]

Attachment: Shared Folders icons did display on PERSONAL IMAP accounts

Comment 2

[Karen Huang]

Attachment: But, Shred Folders icons Are NOT displaying on OTHER USER'S IMAP account.

Comment 3

[Karen Huang]

Even this is just IMAP Shared UI, I am still nominating nsbeta1 since this is 
basic IMAP Shared UI for indicating IMAP Shared Folders.

Comment 4

[Karen Huang]

Please reassign if I was wrong.....

Comment 5

[David :Bienvenu]

if we had noticed this a few months ago, it could have made rtm, but at this
point, it's way too late.

Comment 6

[scottputterman]

nsbeta1- per mail triage.

Comment 7

[Karen Huang]

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

Comment 8

[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 9

[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