Move / File Message to #shared Fails when focus has been to multiple teminal directories Moz 1.4 1.6 Linux



MailNews: Message Display
14 years ago
12 years ago


(Reporter: Jay Smith, Unassigned)


Firefox Tracking Flags

(Not tracked)




14 years ago
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040123

This is a little hard to explain.  This problem existed on Mozilla 1.4 and still
exists on 1.6.  I have not been able to find a bug report on it.

When moving / file / filing a message USING THE MENU OR BUTTON, not by dragging,
(from any location, not important), *IF* in the process of doing the action you
accidentally enter a mail directory you did not intend to be in and then go the
correct directory and correct mailbox, the move fails (i.e. message does not get
moved).  Occurs about half of the time that I do this type of action (and get it

We are using: UW IMAP vers 2001a release 15 from Red Hat supplied RPMs (from RH
8 install CD).

Reproducible: Sometimes
Steps to Reproduce:
1. Select message to be moved.
2. Use either menu (Message, Move Message) or "File" button to move message
3. Navigate down into #shared mail directory DEEP structure
4. Accidentally enter a terminal DIRECTORY (containing many mail boxes)
5. Back out (change focus) to correct terminal DIRECTORY
6. HOVER over the target mailbox into which message is to be placed
7. HOLD the HOVER until 'alt text' appears (yeah, it's wrong, but we know that)
8. Click on the target mailbox to execute the move.

Actual Results:  
Half the time the move simply fails / does not occur.  The message stays where
it was and no copy is made in the target mail box.

This happens 6-12 TIMES PER DAY.

Expected Results:  
The message should have been moved to the target mail box.

There does not seem to be any consistent reason for why it works sometimes and
not other times.  It is as if it is related to TIMING and SERVER LOAD.  It
*think* that the longer I hover, the better my chance of success.  However, I
have had it fail when continuing hovering for as much as 10 seconds after the
alt text has appeared.

The Mozilla is running on a RedHat 8 server (intel) and is viewed on PC
workstations using Cygwin/XFree86 (not that that the workstations should matter;
they are just displaying)

The IMAP "#shared" folder structure is DEEPer than most people seem to use. The
leading underscores in some directory names are to force desired order of
appearance. Directories only contain mail folders and/or directories.  IF a
directory would otherwise only contains directories, then we have already made a
mail folder "_general" [not illustrated in the example below] so that all
directories include at least one mail folder.  We have more than 2000 Imap mail

Structure looks like:

#shared (the IMAP structure)
         a         <------------- this has about 100 mail boxes in it
         b         <------------- this has about 100 mail boxes in it
THE PROBLEM OCCURS if I accidentally first focus on "a" (so that it opens up)
and then change so that focus is on "b" (so that it opens up instead).  [Nothing
special about "a" and "b" -- it could be m and p.

The problem NEVER occurs if I don't accidentally get to the wrong directory.

My problem with this activity (and the accidental wrong directory focus) is
related to bug 190204 -- which has received no attention at all and is a really,
really, really annoying bug / interface quirk.

Comment 1

14 years ago
This problem still exists and is frustrating as ever.

I have started to instead use the keyboard pneumonics to do the filing, but that
is partially broken (differently) and I will report separately on that.

Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail
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
You need to log in before you can comment on or make changes to this bug.