Open Bug 71383 Opened 24 years ago Updated 2 years ago

IMAP Other Users Namespace: Display "Shared Folders/User/" folder hierarchy incorrectly in folder pane

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
All
defect

Tracking

(Not tracked)

People

(Reporter: huang, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [patchlove][c.f. comment 4])

Attachments

(2 files, 2 obsolete files)

Used 03-08-13-Mtrunk build

IMAP Namespace: Display "Shared Folders/User/" folder hierarchy incorrectly in 
folder pane

1)Specify one profile with 4.x preferences with Other Users "Shared 
Folders/User/" setup.
2)Migrated or create this profile in 6.5
3)Actual Results: The folder hierarchy seems to display incorrectly in current 
build folder pane (Please see the following 4.x & current build screen shots)
The "Shared Folders/User/", it treat "/" for subfolder...

Expected results: Should display "Shared Folders/User/" for one level folder as 
4.x screen shot.
QA Contact: esther → huang
Summary: IMAP Namespace: Display "Shared Folders/User/" incorrectly in folder pane → IMAP Namespace: Display "Shared Folders/User/" folder hierarchy incorrectly in folder pane
Summary: IMAP Namespace: Display "Shared Folders/User/" folder hierarchy incorrectly in folder pane → IMAP Other Users Namespace: Display "Shared Folders/User/" folder hierarchy incorrectly in folder pane
Nominating nsbeta1 based on Mach V PRD IMAP Shared Folders
Assignee: mscott → bienvenu
Keywords: nsbeta1
Keywords: nsbeta1nsbeta1+
Priority: -- → P2
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.9
this might be very difficult - 4.x would check if the folder was a namespace and
not add an extra level of hierarchy, but the uri parsing code in 6.x would be
very unhappy with a namespace with the hierarchy delimiter in it that didn't
indicate a level in the hierarchy. Perhaps we could escape the hierarchy
delimiter and set the pretty name to be the namespace - anyway, this is going to
be tricky and have high potential for regressions, fyi.
moving to 1.0
Target Milestone: mozilla0.9.9 → mozilla1.0
moving out.
Keywords: nsbeta1+nsbeta1-
Target Milestone: mozilla1.0 → Future
CCing to myself
Blocks: 160644
CC to myself. I agree with bienvenu's comment#4. 
We can control the hierarchy of folders *when they are created initially* as we
want.
Attached patch patch for test (obsolete) — Splinter Review
This patch works on my iPlanet server just as "4.x screen shot for "Shared
Folders/User/" correct folder hierarchy".

You need to create new account with the otherusers namespace 'Shared
Folders/User/' for test.

Only fresh the folder pane won't let the code work if you already have one such
test account. You need create new *profile* and create new *account* to test.
phillip, we don't use gotos as a general rules.
Ok, I will change it. Thanks! :-)
Attached patch patch for test (obsolete) — Splinter Review
This patch has the same result with attachment 108003 [details] [diff] [review] .

Still a 'goto' in this patch. But if we delete it, I'm afraid we must duplicate
many same lines.

Do you think this will be ok? Thx! :-)
Attachment #108003 - Attachment is obsolete: true
QA Contact: huang → gchan
Product: MailNews → Core
philip, does patch still work?
Assignee: bienvenu → nobody
QA Contact: grylchan → networking.imap
Whiteboard: [patchlove]
Product: Core → MailNews Core
Comment on attachment 108137 [details] [diff] [review]
patch for test

Already bit-rotted, unfortunately.

$ patch -p0 --dry-run < ~/Desktop/tbTestPatches/nsImapMailFolder__CreateClientSubfolderInfo 
patching file nsImapIncomingServer.cpp
Hunk #1 FAILED at 1181.
1 out of 1 hunk FAILED -- saving rejects to file nsImapIncomingServer.cpp.rej
patching file nsImapMailFolder.cpp
Hunk #1 FAILED at 805.
Hunk #2 FAILED at 863.
2 out of 2 hunks FAILED -- saving rejects to file nsImapMailFolder.cpp.rej
Attachment #108137 - Attachment is obsolete: true
Moving back to NEW - there isn't any assignee email.
Status: ASSIGNED → NEW
OS: Windows NT → All
Priority: P2 → --
Whiteboard: [patchlove] → [patchlove][c.f. comment 4]
Target Milestone: Future → ---
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: