Created attachment 134899 [details] Test file In a basic macro with the following steps: 1) Load in hidden mode a Excel 97 file (.xls) with a freeze pane in a sheet 2) Insert a new sheet before then sheet with the freeze 3) Save the file as Excel 97 The expected behaviour is that in the changed file the freeze pane remains but moved with the initial sheet but the observed behaviour is that the freeze pane remains in the sheet with the same original position in worksheet. (example a worksheet with a sheet named "Original" in position 0 with a freeze, insert new sheet named "New" in position 0 and the result is a worksheet with the sheet named "New" in position 0 has the freeze and the sheet named "Original" in position 1 lost the freeze). I have made another test: Loading the file not using the hidden mode the result is the same as expected. Loading the same file as .ods in hidden mode all the freezes are removed (not expected but logical). Saving the file as .xlsx all the freezes are removed. I have attached some files to test: -Download the files "Test.odt", "Test2.odt" and "Test2.xls". -Open the file "Test.odt" with the others files in same folder. -Press the button "test xls file hidden". -In the file "Test2.xls" with a freeze in sheet "Hoja 1" a new sheet is inserted before that sheet (using hidden mode). -The file is saved as ".odt", ".xls" and ".xlsx" -All then changed files are displayed to compare The adjacent buttons test the other possibilities: -"test ods file hidden" -> Load a .ods file using hidden mode -"test ods file not hidden" -> Load a .ods file not using hidden mode -"test xls file not hidden" -> Load a .xls file not using hidden mode Versión: 5.2.4.2 Id. de compilación: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 Subprocesos de CPU: 2; Versión de SO: Windows 6.1; Repr. de IU: predeterminado; Configuración regional: es-ES (es_ES); Calc: group
Created attachment 134900 [details] Test file 2
Created attachment 134901 [details] Test file 3
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Tested with an updated version but not 5.4 Actually I can't install this version. Same behaviour as indicated in the bug report. Status not updated. I will try in another PC. Versión: 5.3.5.1 Id. de compilación: 020db1aa8142e57290f8a21e4df31185392d0e38 Subproc. CPU: 2; SO: Windows 6.1; Repres. IU: predet.; Motor de trazado: HarfBuzz; Configuración regional: es-ES (es_ES); Calc: group
Finally tested with the latest version in another PC. Same behavior as reported. Versión: 5.4.0.3 Id. de compilación: 7556cbc6811c9d992f4064ab9287069087d7f62c Subproc. CPU: 2; SO: Windows 6.2; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group
(In reply to Luis from comment #0) > -Download the files "Test.odt", "Test2.odt" and "Test2.xls". > -Open the file "Test.odt" with the others files in same folder. > -Press the button "test xls file hidden". > -In the file "Test2.xls" with a freeze in sheet "Hoja 1" a new sheet is > inserted before that sheet (using hidden mode). > -The file is saved as ".odt", ".xls" and ".xlsx" > -All then changed files are displayed to compare All freezes removed in all sheets with xlsx and ods. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: df48f780e3baf3f82fbe9024c94fccc15a84d53d CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on August 18th 2017 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
** 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 Luis, 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 Luis, 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