Description: I have a very wide sheet that I use split screen to open a narrow left hand column with the first column always visible. When I close the app and come back later, the first column is not quite visible because the position of the split control has shifted left slightly. Steps to Reproduce: 1.Open narrow left split 2.Save and exit. 3. Reopen - Split will move a 10pt spacing each cycle of Save/Open until it evaporates. Actual Results: "||" represens the scroll icon, "|" represents a cell boundary A || A | B | C 12345||12345|Hello Save, Close Reopen 1234||12345|Hello Save, Close Reopen 123||12345|Hello etc. Expected Results: Should be stable across saves. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: I suspect it's the save function, since when you close the sheet without changes, it doesn't SAVE, and doesn't creep.
Created attachment 175839 [details] Simple test case
Repro with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL But on the third time of save-load doesn't happen. As the file, it's saved on MSO format, can be a little difference on same unit used.
It did it ten times before the column label was engulfed, and it became difficult to see the change, although it kept changing.
I should add that I'm saving files as xlsx format.
Easy to reproduce with Save - File - Reload, multiple times Also Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Dear jjgurley, 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