Description: When using autofilter against a large (ish) list (3 columns, 5000 rows, csv format, unique id - email address - name) typing in the filter box causes a delay, the delay causes the user input to be entered in a different order to keys pressed. example actual - booking, hotmail, @guest. result - bokingo, hotmail, @gust.e the number of results in the list matching the search query influences the resulting level of disorder in the input. adding a delay in the processing of the characters as opposed to immediately trying to sort per letter, if you wait for each letter to restrict the list, the performance increases dramatically for each additional letter entered. I get the same issue on ubuntu 17 as i do on fedora 21 Steps to Reproduce: 1.create a large csv approx 5000 rows 2.ensure that at least 2000 rows share a common word or phrase 3.add autofilter to the csv data 4.enter the common word or phrase into the search box, typing at normal speed 5.wait for the word to appear, words longer than 7 characters are likely to be garbled, if not, elongate the list or use a longer word the problem will show Actual Results: user input is garbled Expected Results: user input is entered correctly Reproducible: Always User Profile Reset: Yes Additional Info: OpenGL (or in my case "hardware acceleration") being toggled on or off makes no difference. User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36
Hi David, Can you provide such a test file? This would be really very kind. Thank you.
Yeah, ive included a csv of sample data, hashed, except for the portion after the @ on emails ending guest.booking.com if you autofilter this csv and try typing in "booking" you will get the bug if it is reproducible.
Created attachment 141658 [details] sample data
Not reproduced. Version: 6.0.4.2 (x64) Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group Arch Linux 64-bit Version: 6.0.4.2 Build ID: 6.0.4-1 CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group
Created attachment 143400 [details] I can't reproduce it in LibreOffice 6.2
I can't reproduce it in Version: 6.2.0.0.alpha0+ Build ID: 67f3063b7c334d4d5c59132d90b938671aad09f0 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded Could you please paste the info from Help - about LibreOffice ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the information has been provided
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20190111
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20190321