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

            Bug ID: 152327
           Summary: "Select unprotected cells" when no cells are
                    unprotected makes data entry impossible
           Product: LibreOffice
           Version: 6.3.6.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: high
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]
            Blocks: 107450, 109139

Steps:

1. Open Calc
2. Edit > Select > Select unprotected cells (nothing is selected, as expected,
given that all cells a protected by default)
3. Enter any data in a cell
4. Click out or press Enter

Actual results:
Data entered in cells instantly disappears.

This issue does not happen when one or more cells are unprotected (with Edit >
Cell protection).

Workarounds:
- Saving and reloading the document does restore the ability to add data to
cells.
- Selecting a cell range before entering data fixes the issue.

Versions:

Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

A master build from today:

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 01a3cc1e55034f7703219d4bbb209de7c37bf07b
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Already in:

Version: 6.3.6.2
Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; 
Locale: en-AU (en_AU.UTF-8); UI-Language: en-US
Calc: threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107450
[Bug 107450] [META] Cell and sheet protection bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109139
[Bug 109139] [META] Cell selection bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to