When you copy/paste, you can paste in a protected cell. Steps to reproduce: - Open calc - Create a second sheet - Protect the second sheet - Copy some random content - Come back on the first sheet and select both sheets - Paste content -> It will bypass protection on the second sheet This bug affects master and I'm working on it.
Gerrit patch: https://gerrit.libreoffice.org/#/c/36130/
Can you please explain why this blocks Bug 96157 and should it be marked as it's duplicate?
(In reply to Timur from comment #2) > Can you please explain why this blocks Bug 96157 and should it be marked as > it's duplicate? Hello Timur, it's a duplicate but with more informations. You can mark the other as duplicate. Thanks, Jean-Sébastien Bevilacqua
*** Bug 96157 has been marked as a duplicate of this bug. ***
From Bug 96157: attachment 120897 [details] is 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...
This one is marked as "LibreOffice" while I guess it's Calc only. True there are also Writer bugs for protected cells in table but in different bugs. Jean-Sebastien, could you review your code and remarks once more? Asking as a non-dev who sees that you tried to solve this issue.
Dear Jean-Sebastien Bevilacqua, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Jean-Sebastien Bevilacqua, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I don't know how I marked duplicate, but I don't repro steps from Description with older LO. So I mark duplicate the other way around. *** This bug has been marked as a duplicate of bug 96157 ***