Issue 126271 - Disabling of locked cell selection not working correctly
Summary: Disabling of locked cell selection not working correctly
Status: CLOSED DUPLICATE of issue 123703
Alias: None
Product: Calc
Classification: Application
Component: formatting (show other issues)
Version: 4.1.1
Hardware: All All
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 126280 (view as issue list)
Depends on:
Blocks:
 
Reported: 2015-04-26 14:05 UTC by bfallert
Modified: 2017-05-20 09:52 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
requested document (15.44 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-04-29 13:54 UTC, bruce
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description bfallert 2015-04-26 14:05:34 UTC
I have a spreadsheet where I need to restrict cell movement to only the unprotected cells.  When protecting the sheet, I deselect the option for allowing the user to select locked cells.  Initially, all works as expected.  The cursor only moves among the unprotected cells.  If I click on a protected cell with the mouse, the cursor will not move to that cell.  However, if I close the spreadsheet, then reopen it, I can select locked cells.  The locked cells still cannot be modified, but if I use the mouse, I can move the cursor to locked cells.  I have tested this on Windows and Mac.
Comment 1 orcmid 2015-04-26 14:38:01 UTC
(In reply to bfallert from comment #0)
However, if I close the spreadsheet, then reopen it, I can select locked
> cells.  The locked cells still cannot be modified, but if I use the mouse, I
> can move the cursor to locked cells.  I have tested this on Windows and Mac.

What format are you saving the spreadsheet in?
Comment 2 bruce 2015-04-28 18:28:07 UTC
same issue for me exactly
Comment 3 Marcus 2015-04-28 18:46:09 UTC
*** Issue 126280 has been marked as a duplicate of this issue. ***
Comment 4 oooforum (fr) 2015-04-29 07:30:11 UTC
According to comment 1, thanks to attach a sample document.
Don't forget to provide any information like password if this document is protected.
Comment 5 bruce 2015-04-29 13:54:32 UTC
Created attachment 84713 [details]
requested document

per request attached is a copy of the offending document
Comment 6 Oliver Brinzing 2015-04-29 17:58:22 UTC
.
Comment 7 oooforum (fr) 2015-06-02 13:29:55 UTC
(In reply to bruce from comment #5)
> per request attached is a copy of the offending document
Now, could you provide a step-by-step to reproduce?
Comment 8 oooforum (fr) 2015-08-23 18:30:58 UTC
No news since +30 days: closed

Feel free to provide the step-by-step required. So this Issue may be closed or
progressed as necessary - otherwise the issue may be Resolved as Invalid in the
future.
Comment 9 Bill 2015-08-24 12:11:27 UTC
Step by step to repeat the issue:

Open a new spreadsheet
Enter misc. data into a handful of cells
Select about half of these cells
Go to Format > Cells > Cell Protection
Uncheck the Protected option
Go to Tools > Protect Document > Sheet
Enter and confirm a password
Uncheck the Select Locked Cells option
You should now only be able to select the unprotected cells in the spreadsheet.  You should not be able to select the locked cells.
Save the spreadsheet and quit OpenOffice
Reopen the spreadsheet
Now, you are able to select any cell, which should not be the case.  You cannot edit the locked cells, but you should also not be able to select them.
Comment 10 mroe 2015-08-24 14:49:14 UTC
Can confirm the behaviour with AOO 4.1.1 under Ubuntu 64.

1. Simply open the attached document.
You can select all cells.
2. Unprotect the sheet. (Tools → Protect Document → Sheet)
Now you can edit all cells.
3. Protect the sheet. (Tools → Protect Document → Sheet)
Deselect [_] Select locked cells. → [OK]
You can only select the unprotected cells.
4. Save the document.
5. Reload the document and goto 1.
Comment 11 j.nitschke 2015-12-21 04:00:15 UTC
duplicate, this bug had already areport

*** This issue has been marked as a duplicate of issue 123703 ***