Closed Bug 118916 Opened 23 years ago Closed 21 years ago

file picker does not respect SetDisplayDirectory() when opening in "pick folder" mode

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 89325
mozilla1.0.1

People

(Reporter: sspitzer, Assigned: law)

References

Details

file picker does not respect SetDisplayDirectory() when opening in "pick folder"
 mode

here's the mailnews code for "saving all attachments", which wants you to pick a
folder.

   filePicker->Init(
        nsnull, 
        GetString(NS_LITERAL_STRING("Save All Attachments").get()),
        nsIFilePicker::modeGetFolder
        );

    rv = GetLastSaveDirectory(getter_AddRefs(lastSaveDir));
    if (NS_SUCCEEDED(rv) && lastSaveDir) {
      filePicker->SetDisplayDirectory(lastSaveDir);
    }
    
    filePicker->Show(&dialogResult);
    if (dialogResult == nsIFilePicker::returnCancel)
        goto done;

the call to SetDisplayDirectory() doesn't work.  so even though we are trying to
persist the last directory the user chose, it doesn't work.

this blocks bug #108542
Seth,  do you see the same problem on all platforms?  There are different
implementations of nsIFilePicker so we may have to fix this is three different
places.

I can definitely take care of the Win32 implementation and can manage the Linux
(.js) one, too.  The Mac is a different story, but most likely this isn't broken
there (I hope).

I'm setting the target milestone to match bug 108542.
Target Milestone: --- → mozilla1.0.1
Almost certainly a dupe of but 89325 - and that bug even has a patch ;)
Summary: file picker does not respect SetDisplayDirectory() when opening in "pick folder" mode → file picker does nenot respect SetDisplayDirectory() when oping in "pick folder" mode
Sorry
Summary: file picker does nenot respect SetDisplayDirectory() when oping in "pick folder" mode → file picker does not respect SetDisplayDirectory() when opening in "pick folder" mode
Marking as dupe of 89325, which has a patch.  All we need now is to work out the
process for moving a confirmed bug with patch into the build, within 18 months
of being reported and a fix made.

Yep - 18 months!  It really doesn't encourage community participation :(

*** This bug has been marked as a duplicate of 89325 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.