132927 - Need IMAP Shared Folders icons for Shared "Inbox, Sent, Trash, Drafts and Templates" default/special folders

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Karen Huang]

Used 03-22-05-trunk build

Need IMAP Shared Folders icons for Shared "Inbox, Sent, Trash, Drafts and 
Templates" default/special folders

Based on the UI Spec as following and refer to bug 28756, we have IMAP shared 
folders icons for general shared folder, but we still need IMAP Shared Folders 
icons for Shared "Inbox, Sent, Trash, Drafts and Templates" default/special 
folders for both Classic & Modern Themes:

http://www.mozilla.org/mailnews/specs/folder/#Sharing

Ccing Jennifer.

Comment 1

[Karen Huang]

Nominating nsbeta1 for MachV IMAP shared folders UI.

Comment 2

[David :Bienvenu]

I would recommend not doing this - it's way to late in the game and we'd have to
add a bunch of css that will slow us down.

Comment 3

[jglick]

If we decide to this, the icons that should be used in the folder pane when 
folders are shared, both Personal and Special folders, both Modern and Classic, 
are shown here: 
http://www.mozilla.org/mailnews/specs/folder/images/ShareIcons.gif

The icons should already exist. Marlon Bishop is the guy to see to get a hold of 
 the files as nec.

Comment 4

[David :Bienvenu]

yes, the icons exist and we are using them for folders you share, just not for
other users shared folders - I'm not sure why Karen thinks we need new icons.

Comment 5

[Michael Klose]

I agree with comment #4.  
 
In bug #148460 I propose to change the canonical structure of folder names 
which would make it very easy to identify which are private, which are shared 
and which are public folders, because these would then be under different 
subtrees. 
 
 

Comment 6

[Peep Chaintreuil]

"Junk" needs to be added to the list of folders/icons.

Comment 7

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

[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

Comment 9

[Karsten Düsterloh]

Still valid.