[Libreoffice-bugs] [Bug 117967] On Linux LibreOffice doesn't protect users from accidental content overwrite when a file, opened in a LibreOffice window, was updated outside of that window.

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Mon Jun 4 19:10:29 UTC 2018


https://bugs.documentfoundation.org/show_bug.cgi?id=117967

--- Comment #3 from yury.dubinsky at gmail.com ---
Hello, Jean-Baptiste,
This is a design bug. LO behavior is consistent, but wrong from my point of
view.
Your scenario is right, just it is incomplete. 
Please, add to more steps:
9/  press cancel
10/ press ctrl+S again. At this point you will not get any confirmation, the
content B/foo.odt will be saved. 
The program should confirm with users every time when the timestamp is old.

Also, please, take a look at  step 4. open B/foo.odt. Why is the symbolic link
opened as an independent file? The advanced text editors on Linux easily
recognize symbolic links and process symbolic links as target files. I mean
such editors as gvim/vim, emacs, geany,  visual studio code, kate, and many
more. 

In my career I was presenting Linux and LO to few small offices, and I know
many real cases when users, with Windows background,  lost content. Let’s take
another look at your scenario from human perspective. 
Step 8: an user, familiar with Windows shortcuts, could be not aware that
B/foo.odt is a symbolic link. Getting a warning message will entirely surprise
this user. Then, normal actions from users are: cancel saving and rapidly move
all changes made in B/foo.odt to A/foo.odt.
Both windows have to same title, so, it's very easy to make a mistake and press
ctrl+S in the wrong window. Especially when users can assume that in case of a
wrong window LO will warn again. However, LO doesn't do it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20180604/13555e90/attachment-0001.html>


More information about the Libreoffice-bugs mailing list