https://issues.apache.org/ooo/show_bug.cgi?id=122659

            Bug ID: 122659
        Issue Type: ENHANCEMENT
           Summary: Save read-only not reliable
           Product: General
           Version: pre AOO 3.4.0
          Hardware: PC
                OS: Windows 7
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: ui
          Assignee: issues@openoffice.apache.org
          Reporter: rainerbielefeld_ooo...@bielefeldundbuss.de
                CC: issues@openoffice.apache.org

Steps how to reproduce with  "AOO 4.0.0-Dev – German UI / locale
[AOO400m2(Build:9701)  -  AOO400m2(Build:9701)  -  Rev. 1497734 Rev.1496828 
2013-06-28]" on WIN7 Home Premium (64bit)", Common 4.0-dev User Profile:

1. From AOO Start Center open new Writer Document
2. type few characters
3. Menu 'File -> Properties -> Security' check "File Sharing Options -> Open 
   file read-only" <ok>
4. Save as  "sample.odt"
5. Menu 'File -> Close'
6. Reopen from menu 'File -> Recent documents'
   Expected: Opens write protected
   Actual: You can edit the document, not opened read-only

The behavior might be more or less intended, because it should be possible to
break the write protection "somehow", for example by saving the document under
a new name, and during proceeding you saved "Untitled.odt" as "sample.odt"
(under new name).

But that might be unexpected, may be user simply wanted to correct a typo in
the file name or similar when he saved the document. The Document still is
write protected after it has been saved, nothing indicates that the document no
longer will be "read-only" after save and reopen. 

So I think there should be a message "Document will loose write protection" or
similar when the write protected document will be saved, or the saved document
(with new name) should become editable immediately, or something else should
indicate that after reopen the document will no longer be write protected.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Reply via email to