Created attachment 142969 [details] Example file from Excel with a Validity value set as macro condition If we try to run the macro in the attached file, the Sheets will not hide if we set the L9 cell to OK using validity setting and the Object Catalog will not work correctly. Steps to reproduce: 1. Create a new spreadsheet with Microsoft Excel 2016/2013 2. Set a validity for a cell (“L9”) and choose the List type. Set two value (OK and NOT OK) 3. Create 8 Sheets. 4. Add this macro code to the Sheet1: Private Sub Worksheet_Change(ByVal Target As Range) If Target.Address = Me.Range("L9").Address Then If Target.Value = "OK" Then Sheets("Munka8").Visible = True Sheets("Munka7").Visible = True Sheets("Munka6").Visible = True Sheets("Munka5").Visible = True Else Sheets("Munka8").Visible = False Sheets("Munka7").Visible = False Sheets("Munka6").Visible = False Sheets("Munka5").Visible = False End If End If End Sub 5. Set the value of the “L9” cell to “OK” and NOT OK. (It will work) 6. Save the file as *.XLSM. 7. Open the file with LibreOffice Calc and set the value of the “L9” cell to “OK” and “NOT OK”. (It will not work) 8. Save as the file in LibreOffice Calc. 9. Open in Microsoft Excel. Actual results: The macro does not work. If we open the file in LibreOffice Calc and open the Object Catalog, we can see the Document Objects. But If we double click on the “Sheet1” (we use a macro here) LibreOffice adds a new Sheet1 module to the Modules and we cannot open our macro code from the Object Catalog. If we save the file and reopen with Microsoft Excel the Object Catalog will be completely wrong. Expected results: The macro should work and the Object Catalog should work correctly if we want to open a Document Object. Version: 6.0.0.0.beta1+ Build ID: 29228e83df009cf76ac819ed024527be1092f065 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:libreoffice-6-0, Time: 2017-12-04_23:15:34 Locale: hu-HU (hu_HU); Calc: group threaded
Created attachment 142970 [details] The example file saved by Calc
Created attachment 142971 [details] The original and the saved file in Excel and Calc side by side
Created attachment 142972 [details] The original and the exported files structure in Excel
Repro with document Win 8.1 32-bit MSO 2013 LibreOffice Version: 6.2.0.0.alpha0+ Build ID: e1a77d0affef507d597e7dceb5514073658332df CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-27_04:47:54 Locale: fi-FI (fi_FI); Calc: group threaded
Reproduced in: Version: 7.0.2.2 (x64) Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994 CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: default; VCL: win Locale: en-AU (en_AU); UI: en-US Calc: threaded
Dear Gabor Kelemen, 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
Dear Gabor Kelemen (allotropia), 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