MOVETO to new foldername at level 4 or higher went terminated too soon



MailNews Core
14 years ago
9 years ago


(Reporter: David Riker, Assigned: (not reading, please use instead))


Windows 2000

Firefox Tracking Flags

(Not tracked)



(4 attachments)



14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113

After level 4 or higher FOLDERNAME , the MOVETO operation terminated or
disapeared itself too soon.  While do at level 4 or 5, noticed at  level 2
Foldername changed errorly to different foldername causing termination of MOVETO
operation at level 4 or 5.

I am unable to enter new foldername at level 4 or 5 because the MOVETO
processing went terminating after 2 second or change back to level 1 or 2.

Reproducible: Always
Steps to Reproduce:
1. on MAIL, click tools, click message Folders, double click filtername 
2. Check MOVETO. Click folder pulldown at level 1. Click level 2 foldername
3. Click level 3 foldername, Click level 4 foldername, click level 5 foldername
4. Click "choose this folder", Click New Folder, enter new folder name at level 5. 
Actual Results:  
After level 4 or higher, the MOVETO operation cancelled or disapeared itself.
I am unable to add new foldername at level 4 ot 5. MOVETO operation terminated
TOO SOON. MOVETO changes back to Level 1 or 2 even you do not move mouse for at
least 2 second.

Expected Results:  
Stay level 4 or 5 for at least 10 seconds  or more to allow to complete new
foldername at  level 5.

Comment 1

14 years ago
Created attachment 143490 [details]
Demo of Level 1 Foldername

Comment 2

14 years ago
Created attachment 143491 [details]
Demo of Level 2

Comment 3

14 years ago
Created attachment 143492 [details]
Demo of Level 3 Foldername

Comment 4

14 years ago
Created attachment 143493 [details]
Demo of Level 4 Foldername
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.