Closed Bug 263348 Opened 20 years ago Closed 20 years ago

Unable to move a Virtual Folder back to its previous locations.

Categories

(Thunderbird :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: trix, Assigned: Bienvenu)

Details

(Keywords: fixed-aviary1.0)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10

A Virtual Folder can be moved into other locations: The Inbox or into another
folder.  But unable to move the Virtual back to its previous location.

Reproducible: Always
Steps to Reproduce:
1.  Create a Virtual Folder
2.  Move(mouse drag) folder into the Inbox.
3.  Now, attempt to move the folder back to its intial location.

Actual Results:  
Move attempt fails although the root(main POP3) folder does highlight giving the
indication that the move should be allowed.

Expected Results:  
If the Virtual Folder should behave like a normal folder, then moving to prior
locations should be allowed.
Assignee: mscott → bienvenu
Could this bug depends on bug 263990?
Trix, can you try this with tomorrow's build? I suspect this would be a dup, as
Henrik suggested.

*** This bug has been marked as a duplicate of 263990 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
This is not a dupe of bug 263990. I tried to move a virtual folder to another
location which works now. This is be done with the above bug. But moving back to
the original folder doesn't work. JS console shows following exception message:

Exception : CopyFolders [Exception... "Component returned failure code:
0x8052ffff [nsIMessenger.CopyFolders]"  nsresult: "0x8052ffff (<unknown>)" 
location: "JS frame :: chrome://messenger/content/messengerdnd.js ::
DropOnFolderTree :: line 338"  data: no]

There are other strange behaviours when moving a virtual folders between
different real folders. After a while you can't move it until you restart TB.
But this should be tested after the above exception gets killed.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
david the problem is still occuring on todays build 20041015
Attached patch proposed fixSplinter Review
calling ::Delete on the source folder will force the summary file closed, which
will allow us to delete it. And restoring the check that we're reloading the
same folder (but use gPrevMsgFolder to account for virtual folders...) will
prevent the xul content build from causing us to reselect the just deleted
folder, recreating the .msf file we just worked so hard to delete.
Attachment #162602 - Flags: superreview?(mscott)
Attachment #162602 - Flags: superreview?(mscott) → superreview+
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
verified with build from version 0.8 (20041021)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: