Bug Hunting Session
Bug 51473 - FILESAVE: (Windows) Save As dialog offers path to save in improper context
Summary: FILESAVE: (Windows) Save As dialog offers path to save in improper context
Status: RESOLVED DUPLICATE of bug 51149
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-27 04:23 UTC by capkidd
Modified: 2013-01-28 11:31 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description capkidd 2012-06-27 04:23:09 UTC
Problem description: 

Windows only. The Save As dialog every time offers the path to save that was used for the last saved document. And so is exporting to PDF.

Steps to reproduce:
1. Open any text document in Writer
2. Save in any location using Save As dialog. This is Location1
3. Close document or close the entire application
4. Open any text document in a location different to Location1.
5. Try to open Save As dialog. Check the offered path. This will be Location1

or

5. Invoke Export PDF tool. The offered path will be Location1.

Current behavior:
Yesterday I edited a document, saved it, and today I opened a completly different document from a completly different path, maybe, this time from a removable drive - and WTF! Export PDF dialog offers me yesterday's path, from where I must made a thousand clicks to get near the original. 

Expected behavior:
The normal behavior is first to offer the path, where the original document was opened, or system "My Documents" path for newly created documents.

Platform (if different from the browser): 
Windows
              
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5
Comment 1 bfoman (inactive) 2013-01-28 11:31:18 UTC

*** This bug has been marked as a duplicate of bug 51149 ***