Description: When inserting a new column within a frozen area, an originally frozen column is pushed out of the range and is no longer frozen. Steps to Reproduce: 1. Create a new spreadsheet in Calc. 2. Add text to at least 5 or 6 columns in row 1. 3. Right click on column D and freeze the columns (This has frozen columns: A, B, C.) 4. Now right click on column C and select "Insert columns before" Actual Results: This will push the columns over, and columns A,B,C are still frozen but the old column C that is now D, is outside of the frozen area. Expected Results: The expectation is that the frozen column would be moved over so that A,B,C,D would be frozen. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info:
Created attachment 149543 [details] demo freeze column
(In reply to huntantr@gmail.com from comment #0) > Expected Results: > The expectation is that the frozen column would be moved over so that > A,B,C,D would be frozen. the current behaviour is inherited from OpenOffice. why do you expect this behaviour is not correct?
I believe this to be incorrect behaviour for this reason. If I have a financial spreadsheet with data in the locked columns, and outside of that there are calculations, if there is a need to add additional columns within the locked area, it then pushes the last column over and breaks all of the formulas plus how the data is to be viewed. If I make a change with in a locked area, that is where the change should be made and the locked area should be adjusted to maintain proper document formatting. Also, this is the behaviour in MS Excel, so users trying to switch won't because of this problem.
(In reply to huntantr@gmail.com from comment #3) > I believe this to be incorrect behaviour for this reason. > Also, this is the behaviour in MS Excel, so users trying to switch won't > because of this problem. That is true, excel 2016 moves the frozen area. Setting issue to „new“.
Dear huntantr@gmail.com, 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
Dear huntantr@gmail.com, 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
Aslo in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 7daf830830609cbb13a01ae55634187718c84d8a CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded