Description: I have some tabular data, let's say - dictionary, in a LibreOffice Calc. Imagine I have English words in column A. So, whenever I enter a new row/record in that file, if the characters match any other previously entered record (if I'm entering same word or word starting with same letters), automatic highlight with suggested duplicate word pops up. The problem is, that this works fine unless the gap between possible duplicates is less than 100 rows. As soon as I enter the duplicate such that it exceeds 100 rows from the duplicate value, highlight doesn't pop-up with suggested duplicate word. This is quite wrong and not consistent, and I really need this function to be available for entire file. Steps to Reproduce: 1. Create tabular data and enter some random words in one column so that you fill up more than 100 rows; 2. Start entering the word written in row 1, in 101st row; 3. Automatic highlight for possible duplicate won't work; however, it works it you enter that word in 100th row. Actual Results: Automatic highlight doesn't work for duplicate values if the gap between duplicates is greater than 100 rows. Expected Results: Automatic highlight should be working for any gap between possible duplicates. Reproducible: Always User Profile Reset: No Additional Info:
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? If the bug is still reproducible please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org /QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
I have removed the profile and re-installed entire software. It's the same. I've reproduced it even on other Windows (8). I'm sorry, but I can't make my file public as it contains sensitive data. Nor I can amend entire file to make it depersonalized.. I have to change all file then. Just take any file with more than 100 rows and try to reproduce, it's quite easy and obvious. Thank you
Created attachment 149693 [details] autoinput demo sorry, i can not reproduce it, if i enter "A" in cell A102, LO will suggest "ABC1" (value from cell A1)
Created attachment 149724 [details] Please try to insert any of first 10 row values into 219th row. See this attachment, please. It did work for some new file which I've created, but it definitely doesn't work for this file. It works exactly as I described (good if gap is < 100 rows)
Now it does not autoinput when gap is > than 200 rows. Try on 200 rows gap, please.
Created attachment 149752 [details] AutoInput Demo with 200 rows
steps to reproduce: - open attachment from https://bugs.documentfoundation.org/attachment.cgi?id=149752 - enter B into cell A219 - "Bullhorn" is displayed, but expected "Baffle" from cell A11 - enter C into cell A219 - "Cash-strapped" is displayed, correct reproducible with AOO 4.1.5
Dear Giorgi, 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
I've updated this bug, according to the instructions received in the email. P. S. Yes, I have now installed latest 7.0.5 (longest tested) version of LO, and the bug is still present. It's still on 200 rows distance. I'm not sure if this would be helpful, but for any case, including Version Information details (as I didn't quite get what "leave a comment that includes the information from Help - About LibreOffice" means.. only filling the forms or copying the detailed info.. so copying it here): Version: 7.0.5.2 (x64) CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Dear Giorgi, 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