https://bugs.documentfoundation.org/show_bug.cgi?id=159717
Bug ID: 159717
Summary: Lock file warning dialog promotes data disaster
Product: LibreOffice
Version: 7.5.5.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
Description:
Use Case:
We are using LibreOffice at our office. Our documents reside on a server share
that everybody can access. We rely on the lock file mechanism to prevent people
from editing the same document at the same time.
Context:
When opening a file, the lock file mechanism allows Libre Office to warn users
about a document being already open at another computer. Recently, this dialog
has changed and now easily allows to open a document while ignoring the lock
file.
Issue:
In my opinion, the “Open” button is just too prominently placed. As one is used
to click on “Open” buttons, people tend to use it without much thinking.
However, this button overrides the lock file mechanism and as soon as the user
who clicked on the “Open” button closes the document, data disaster happened:
a) on saving data, the user who had the lock in the first place will overwrite
any changes made by the user who clicked on the “Open” button
b) any other user will be able to open the file without being informed about
the document being already open as the lock file has been removed.
Suggestion:
- Allow to remove/disable the “Open” button in this dialog
- Modify the dialog so that “Open” is not that prominent (e.g. that it is
smaller or that a warning pops up when clicked)?
Steps to Reproduce:
1) Open a document (on a server share) at PC1
2) Open the same document at PC2. Click "Open" button in the "Document in use"
dialog
3) Close the document at PC2.
Actual Results:
The lock has been removed.
Expected Results:
The user should have been instructed by the dialog at step 2) to open the
document in read only mode instead.
Reproducible: Always
User Profile Reset: No
Additional Info:
I think this is a UX design issue rather than a technical issue.
--
You are receiving this mail because:
You are the assignee for the bug.
