243721 - Offline: cannot "Create New Folder" or "new subfolder" for IMAP

Status: NEW

(SeaMonkey :: MailNews: Backend, defect)

Description

[John Kubiatowicz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421

Offline access is very important to me. 

So, on a recent trip I was disappointed to find that I was unable to creat new
subfolders when offline. I was busy filing my backlog of email and wanted to
create a new folder.  The option "Create New Subfolder" (right click on other
folder) was grayed out and unavailable.  

Later, when back online, I had no problem creating a subfolder in the same place. 

Note that the option "Create New Folder" is also grayed out at toplevel when
offline.

Reproducible: Always
Steps to Reproduce:
1. Go offline
2. Try to create a subfolder or folder
3. 

Actual Results:  
Nothing -- option is grayed out.

Expected Results:  
Made it possible to create new folder/subfolder.  This worked on Netscape 4.79
-- my last major IMAP experience.

Comment 1

[John Kubiatowicz]

Note that this problem seems to still exist in 7.1 RC 2.

Comment 2

[John Kubiatowicz]

Um... I seem to be dyslexic tonight.  I meant: This bug still seems to exit in
Mozilla 1.7 RC 2.

Comment 3

[David :Bienvenu]

yeah, that got cut at the last moment years ago and no one complained until now.
If I remember correctly, I had it almost working...I'll look into it.

Comment 4

[John Kubiatowicz]

(In reply to comment #3)
> yeah, that got cut at the last moment years ago and no one complained until now.
> If I remember correctly, I had it almost working...I'll look into it.

Thanx!  Much appreciated.

Comment 5

[Bruce Wolfe]

This is new to this build.
In build 2004082608, right click on a folder to create a subfolder offers this
error message:

XML Parsing Error: syntax error
Location: chrome://messenger/content/newFolderDialog.xul
Line Number 40, Column3:

  -->
--^




(In reply to comment #4)
> (In reply to comment #3)
> > yeah, that got cut at the last moment years ago and no one complained until now.
> > If I remember correctly, I had it almost working...I'll look into it.
> 
> Thanx!  Much appreciated.
> 

Comment 6

[Henning Schnoor]

Hi,

this bug is still present in the current Seamonkey version - if anyone has a fix, this would really be appreciated.