Closed Bug 330544 Opened 19 years ago Closed 19 years ago

"save all" loads last saved to dir, but doesn't allow saving to it again. (without going one dir up)

Categories

(Thunderbird :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 312475

People

(Reporter: janklopper, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 The save all dialog in thunderbird on linux (ubuntu) allows you to select a folder in which to save the attachements, It also loads into the last saved folder on default. If there's is no folder selected (the way it opens by default), you should just be able to click the "save" button instead of going up on folder, and then selecting the folder you just came from. This step is not needed, and while i guess its a GTK issue, someone should fix it. If this is indeed a gtk bug, let me know, il take it downstream, and see if the gtk guys are willing to fix it. Reproducible: Always Steps to Reproduce: 1.save a couple of files to your "downloads" folder by soing save all on the attachements list. 2.try and save from an other email, notice how you are now inside the downloads folder, but are not allowd to click the save button 3.go up one folder, select the downloads folder, and then press save. Expected Results: offer me a save button, anytime, even if im not selecting a folder. If none is selected, just save to the current folder. I guess this is just an anoying bug, but it one of those little things newbee's/coverts wil complain about.
Related to bug 312475?
(In reply to comment #1) > Related to bug 312475? > hmm could be, Il try and update to that version, and see if its solved (but doesn't the linux build use native filepickers anyway?)
*** This bug has been marked as a duplicate of 312475 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.