Created attachment 84249 [details] File showing the problem. Try typing a number into the currency column. Problem description: Using Formatting of empty rows using the Paste Special command is not preserved across saves in .xlsx documents Steps to reproduce: 1. Create a new calc document. 2. Create a row of data in 2 or 3 columns 3. Apply formatting to each column (alignment, number format, whatever) 4. Highlight and copy the row of data 5. Paste the formatting only into all the blank cells below your data, through row 25. (Use CTRL+Shift+v and uncheck everything except "formats"). 6. Save as .xlsx 7. Type something into one of the newly formatted rows to confirm that the formatting was applied. DO NOT SAVE. 8. Close the document and reopen it 9. Type something into a formatted row. Notice that the formatting is no longer there. See attached example (test.xlsx) Current behavior: Formatting of blank rows is lost after save Expected behavior: Formatting should be preserved. WORKAROUND: I've noticed that if any content is present in one of the rows that is formatted (even if it is outside the columns that are formatted), then the pasted formatting will be retained UP TO THAT ROW. In the attached example (workaround.xlsx), I have inserted text in cell D21. I pasted formatting into columns A,B, and C through row 25. The formatting is preserved across saves for columns A,B, and C only through row 21. Operating System: Linux (Other) Version: 4.1.0.4 release
Created attachment 84250 [details] File illustrating a partial workaround
Thank you for reporting this issue! I have been able to confirm the issue on: Version 3.6.6.2 Platform: Ubuntu 13.04 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm this problem on an earlier release I am changing the version number as version is the earliest version that we can confirm the bug, we use comments to say that the bug exists in newer versions as well. Marking as: New (confirmed) Major - loss of data, this is really arguable but I'm trying to be consistent so major it is Low - you can reapply styles relatively easily but still, should be preserved Version: Changing to 3.5.0 beta0 as I can confirm pre-bibisect. Version reflects oldest version where we see the problem, I thought this might be a regression but apparently not, probably inherited from OOo + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Also confirmed with LO 3.3.0.4, 4.0.6.2, 4.2.6.3 - Ubuntu 12.04 x86 All pasted format in empty cells always back to Number|Standard format after filesave. Tried updating summary for clarity & differentiate with Bug 71897
** 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 on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
I can still reproduce this bug in LibO 5.0.2.2 x64 (Windows). I followed the exact steps described in the first post.
Could you please check if you: 1. Create xlsx document with MS Excel with this example (it should work there 2. Open xlsx document created by MS Exce, and save it as xlsx 3. Check if this bug is reproducible with that scenario It will be much easier to compare these two files (Original Excel and converted by LibreOffice) and fix that.
The solution for this issue will be the same as for https://bugs.documentfoundation.org/show_bug.cgi?id=46738
Created attachment 126531 [details] File with custom style up to line 25 created with MS Excel 2010
Created attachment 126532 [details] File after writing by LO 5.1. Styles in empty rows were not preserved
** 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
I can't repro it in Version: 6.3.0.0.alpha0+ Build ID: 3c964980da07892a02d5ac721d80558c459532d0 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded Status->WFM