In Calc, have a sheet with some protected cells. Select a row or more containing some protected cells. Mouse move those rows. Move not possible, but there should be a warning message "Protected Cells Cannot be Modified".
Noting that if such a protected row is "moved" onto an unprotected row, the action _still_ copies the contents to the target (but doesn't remove the contents on the source row). Same behaviour with a cut-and-paste. I agree that a message is needed, but I'm wondering if it needs to be different depending on the case, e.g: - source is protected, target isn't: "Source contents not removed because cells are protected." - cut action on protected cells: "Contents were copied but not removed because cells are protected" - both source and target are protected: "Protected cells can not be modified." (the stock message) UX/Design team, what do you think? Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 40617d867346956588ac023511f31210107217f4 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same in OOo 3.3.
Or we don't copy neither show the copying rectangle on moving the row. Too many warnings spoil the broth.
(In reply to Heiko Tietze from comment #2) > Or we don't copy neither show the copying rectangle on moving the row. Too > many warnings spoil the broth. I think this silence could seem like a bug to users who don't realise the source is protected... But what you suggest is online Office 365's behaviour: cutting a protected source is silently unallowed. Looks like it's generally less chatty and only displays the warning message when trying to enter edit mode on a protected cell, or drag-filling it.
The missing feedback while moving should be a sufficient indicator.
(In reply to Heiko Tietze from comment #4) > The missing feedback while moving should be a sufficient indicator. Possibly. Do you have a reasonable idea of the situation where a warning is given, or not?
We discussed the topic in the design meeting. The conclusion is to use the stock message "Protected cells can not be modified." (not least to save the l10n team from additional work). In addition, the cursor should not change if DnD is not possible (or show a blocking symbol).
Dear Timur, 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