Summary: | EDITING: Can't delete unprotected rows in protected document | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Mark C <mark.coolen> |
Component: | Spreadsheet | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | CC: | dtardon, LibreOffice |
Version: | 3.4.4 release | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | BSA | ||
i915 platform: | i915 features: | ||
Attachments: | Sample0.ods |
Description
Mark C
2011-12-05 08:53:24 UTC
I am pretty sure that this is a user error. You can not do changes that would touch position of protected contents, so in my "Sample0.ods" you only can delete rows/columns below/behind the protected cell. Help and documentation seem to be a little vague concerning these facts, in the Calc Manual under "Cell protection" I read "Use the Cell Protection options to protect cells against certain types of editing" @Mark C Please attach a sample document! Created attachment 54132 [details] Sample0.ods See comment 1! I understand what you're saying, but this is different from the behaviour of MS Excel and breaks compatibility with it. Corel's Quattro Pro does have the same behaviour though ;-) interestingly enough. Your attachment is exactly what I produce as well. Mark MS Office 2010 has more fine-grained control over protection. You can set various levels, including the ability to delete rows, but this affects the whole sheet, whether or not there are protected cells. Gnumeric ignores my sheet protection :-( So at least we should have selectors. Not only "Protected", but - Protect Cell(s) contents - Protect Cell contents' position in the sheet. For my needs that would be useful. But we additionally have to keep in mind compatibility to other programs and ODF and and... @David: Can you help with ODF knowledge or should this be handled by Spreadsheet team? Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material This problem is still present on 4.2.5.2 running under Arch Linux. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.