Created attachment 120897 [details] Video of the bug A1 B1 and D1 are unprotected, but C1 is protected A2 B2 and D2 are unprotected, but C2 is protected Clic on A1, Ctrl-Clic on B1 and D1 Sheet protection is enabled with no selection on protected cells. Move to B2, paste... D2 witch is protected is affected by the paste. It should not...
If you are using 4.2, could you test with version 5 to see, if the problem still exists? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Yes, with libreoffice 5.0.2.2 and OpenOffice 4.1.2.
Reproduced, C2 is affected. I tried to find a duplicate report, but failed. Win 7 Pro 64-bit, Version: 5.0.3.2 (x64) Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: fi-FI (fi_FI) Version: 5.2.0.0.alpha0+ Build ID: a7c3a2a9be83686657c06f37d521f9f6d2004ddd Threads 4; Ver: Windows 6.1; Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2015-11-28_04:39:18 Locale: fi-FI (fi_FI)
Importance MINOR ! Not so MINOR when you risk to delet protected data...
(In reply to Olivier MORIN from comment #4) > Importance MINOR ! > > Not so MINOR when you risk to delet protected data... Workaround is pressing undo. https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Minor - Does the bug require users to not use some feature? Yes, you can't use multi-selected paste on protected cells.
Reproducible on 5.4. I'm working on it
Although this one is older, Bug 106965 is being worked on, so I mark this one as a duplicate. *** This bug has been marked as a duplicate of bug 106965 ***
IMO this is Major, as it's a breach of protection, if aimed at other users, not the creator.
Created attachment 182397 [details] Sample ODS A1 B1 and D1 are unprotected, but C1 is protected A2 B2 and D2 are unprotected, but C2 is protected Click on A1, Ctrl-Clic on B1 and D1, copy Move to A2, paste... C2 which is protected becomes unprotected. Repro 7.5+.
*** Bug 106965 has been marked as a duplicate of this bug. ***
Dear Olivier MORIN, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug