290936 - Can NOT move mail to subfolder

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Timothy Huang]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050417
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050417

With the recent latest build, I can not drag a mail into a subfolder. I have
three subfolders under the "InBox" main folder (in the same level, there are
also other folders). When I tried to move a mail into one of these subfolder, it
will go into one of the folder of the same level of the "InBox" folder, but not
the subfolder I want.

However, I still can move that mail into the subfolder by using the menu command.

Reproducible: Always

Steps to Reproduce:
1. (Create some subfolders under the InBox folder.)
2. Try to move a mail into one of these subfolders.
3. It will go into one of the folders of the same level of the InBox
4. Use the menu command to move the mail into the subfolder.

Actual Results:  
as described above.

Expected Results:  
fix it. In previous builds, I never encountered this problem. Something may
accidentally screwed up in this latest build.

Comment 1

[WADA:World Anti-bad-Duping Agency]

Builds after 4/14 build have regressions after Bug 289792, and 4/17 & 4/18 build
contains partial fix only for the regressions.
See blocking bugs of Bug 289792 and read Bug 289792 comment #28.

Does problem occur on 4/19 or later builds?

Comment 2

[Timothy Huang]

(In reply to comment #1)
> Builds after 4/14 build have regressions after Bug 289792, and 4/17 & 4/18 build
> contains partial fix only for the regressions.
> See blocking bugs of Bug 289792 and read Bug 289792 comment #28.
> 
> Does problem occur on 4/19 or later builds?

4/22/2005 With the /21 latest build, the same problem came back -- can not move
an email into subfolder.

Comment 3

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

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.