129141 - not showing pretty names for special folders in subscribe dialog.

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[(not reading, please use [e-mail] instead)]

not showing pretty names for special folders in subscribe dialog.

spun off from 57440

naving had (has?) a fix for this, but I'd like to try something simpler first.

I think that there might be a simple fix for that issue.

I think we can do this:

the subscribe datasource will call 
nsSubscribableServer::GetLeafName(const char *path, PRUnichar **aLeafName) 
to determine the pretty name to show in the subscribe UI.

in ::GetLeafName() I think we could build up the folder uri (using path) and
then use the msg folder datasource to get the resource for that uri, and then QI
to nsIMsgFolder and then get the pretty name attribute, and return that.

we should spin up a new about about how the subscribe UI does not match the
folder pane UI, and try this approach first.

Comment 1

[Navin Gupta]

I didn't file a bug on this issue because this was a wont'fix issue. 

Comment 2

[ji]

Nominating for nsbeta1, since on a localized build, the subscribe window shows
default folder names in English while the folder pane shows in a native
language, it's very confusing.

Comment 3

[scottputterman]

adding nsbeta1- per mail triage.

Comment 4

[nhottanscp]

nominate for nsbeta1

Comment 5

[marina]

changing qa contact

Comment 6

[Samir Gehani]

Mail triage team: nsbeta1-

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