Steps to reproduce: 1. In a cell, type a multiline text like: foo bar 2. In another cell, start typing: "fo" Expected results: EITHER no autocomplete at all OR autocomplete suggests me the content of the existing cell (no matter how it is visualized) and if I hit enter, the new cell is filled with the same content as the existing one Observed result: Autocomplete shows "foo bar", and if I hit enter, the text "foo bar" is entered into the new cell, in a single line. In other words, it is autocompleting with content that has never been entered in any other cell.
Confirming On Windows 10 Pro 64-bit en-US with Version: 5.1.2.1 (x64) Build ID: 2603b69c5ec5981bb5f053f8ebfd1f3de00a4c29 CPU Threads: 8; OS Version: Windows 6.19; UI Render: default; Locale: en-US (en_US) But, isn't this just the string rules for matching the auto fill simply ignoring the new line white space on the replacement? Don't really see the lack of formatting as an issue. But checking on MS Excel 2007 and the line breaks are picked up for the replacement.
> Don't really see the lack of formatting as an issue. How can that not be an issue?? If it was just the way the autocompleted text is displayed while you type, that wouldn't be an issue, but the de-formatted text (that is the string with the newlines replaced with spaces) is actually inserted into the cell when you hit Enter or Tab. The whole point of autocomplete is that you get to fill a cell with the same text that you had previously entered in some other cell without having to retype it. If you have to edit the cell and go through the text to re-do the formatting (that is insert newlines and delete spaces), what's the point? You may as well go look for the original cell and copy-paste it.
** 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 teo8976, 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 teo8976, 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
Yep, issue still present. Version: 7.2.3.1 / LibreOffice Community Build ID: 20(Build:1) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: an-ES (an_ES.UTF-8); UI: en-US Calc: threaded
Yep, still an issue. Soon it will be 10 years. Pathetic. > 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. This is stupid. It should work the other way around: if you think an old issue might have been fixed, you test it, and if it's fixed then close it.
Created attachment 204636 [details] 98913 - test 25.8.3.2 win-10x64 - steve.contrib@gmail.com up still repro in Version: 25.8.3.2 (X86_64) Build ID: 8ca8d55c161d602844f5428fa4b58097424e324e CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win Locale: en-US (en_CH); UI: en-US Calc: CL threaded + on the screenshot there is an issue with the first letter is capitalized when the text is enter in multilign