Description: MS Office got a feature "Allow Users Edit Ranges" started 2016 version, this feature let user can edit specific cells in protected sheet by key in correct password. But when we open file with this feature in LibreOffice and the specific cells which show pop u ask password become show protected cell cannot modified Steps to Reproduce: 1. Create a excel file with MS Excel and use "Allow Users Edit Ranges" feature and save 2. Open file with LibreOffice Calc and try to edit protected cells with "Allow Users Edit Ranges" feature 3. LibreOffice Calc pop up message box show protected cells cannot modified Actual Results: LibreOffice Calc pop up message box show protected cells cannot modified Expected Results: LibreOffice Calc pop up message box request user key in password then allow modification to cells when password correct Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.4.5.2 (x64) Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6 CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: GL; VCL: win; Locale: en-MY (en_MY); UI-Language: en-GB Calc: threaded
Created attachment 163222 [details] Excel file B3 set allow users edit ranges
Comment on attachment 163222 [details] Excel file B3 set allow users edit ranges this file wrong, please use another file
Created attachment 163223 [details] Cell D4 allow users edit ranges Cell D4 allow users edit ranges
Created attachment 163224 [details] Excel pop up password insert box for check Excel pop up password insert box for check
Created attachment 163225 [details] LibreOffice Calc show protected cells cannot modified LibreOffice Calc show protected cells cannot modified
I set New. You forgot to write password for D4 and for the sheet.
Calc not only doesn't read XLSX option "Allow Users to Edit Ranges" with password, but it has no similar feature, which should be created first. OTOH, XLSX with the option but with no password can have cells edited in LO. Cell Protection status is still shown as Protected.
Dear Paul Tey, 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
Created attachment 193742 [details] Sample XLSX Attached sample did not write pass, so I remove it and add another sample from MSO that has 2 ranges, with and without password. In addition to previous, LO saved XLSX retains protected ranges and they are properly seein in MSO.