Bug 1148201 - LibreOffice Calc loses cell contents when receiving focus
Summary: LibreOffice Calc loses cell contents when receiving focus
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: LibreOffice (show other bugs)
Version: Leap 15.1
Hardware: x86-64 Other
: P5 - None : Critical with 5 votes (vote)
Target Milestone: ---
Assignee: LibreOffice Bug Alias
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-26 15:20 UTC by David Faure
Modified: 2019-09-20 14:05 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Faure 2019-08-26 15:20:08 UTC 
Regression in oocalc 6.2.5.2 compared to 6.1.3:

* Type some content in a cell, in oocalc
* Give focus to another window
* Give focus back to the oocalc window
=> the current cell is emptied, editing mode is started on an empty cell.

Workaround: pressing Esc reverts to the previous contents.
But if the confused user presses Enter instead, those contents are lost.

How does this work? Do you report it upstream if it turns out to be an upstream bug?
Comment 1 David Faure 2019-08-28 14:21:38 UTC 
It's worse than I thought, the user doesn't even have to press Return to lose contents.

Focus a cell with text, focus another window, then click on a different cell in the spreadsheet. The initially focused cell becomes empty (!!!).

This is the worst LibreOffice bug I have ever experienced, silent data loss while using the software, meaning the user might only notice far too late, after making other changes elsewhere, and then even 'Undo' to recover lost data is a real pain since you then lose your actual changes.

Please handle with top priority.
Comment 2 David Faure 2019-09-20 14:05:38 UTC 
Reported upstream at https://bugs.documentfoundation.org/show_bug.cgi?id=127666 given the lack of answer here.