Description: The table on the form does not work search for fields of type ComboBox. If I'm trying to do a search on this form, there simply aren't any of these fields in the field selection list to search for. Search works fine for normal text fields but if you convert them to ComboBoxes then these fields become invisible for search. Because of this, in forms, instead of fields of type ComboBox, you have to make regular text fields and separate ComboBoxes under the table to enter values. Steps to Reproduce: 1 Create table on form. 2 Convert normal fields of the table to ComboBox type. 3 Run form in user mode. 4 Click the search button on the toolbar at the bottom 5 Try to select any of the fields that have been converted to ComboBoxes from the list of fields to search Actual Results: These fields will not be in the list and you will not be able to search for them. Expected Results: The presence of these fields in the list and search for them. Reproducible: Always User Profile Reset: No Additional Info:
Confirming with Version: 6.3.0.0.alpha0+ Build ID: 34ab7b37709fbf889f90b30790573f5ab2521e94 CPU threads: 4; OS: Mac OS X 10.14.2; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded
Reproduced also in ersion: 5.2.5.1 Build ID: 0312e1a284a7d50ca85a365c316c7abbf20a4d22 Threads CPU : 4; Version de l'OS :Mac OS X 10.14.2; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Dear ITicDigger, 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 could not reproduce the problem in LO 7.4.2.3. Specifically, step 5 of OP's reproducer works for me, with all controls, including comboboxes, being listed as searchable fields. Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-PT (pt_PT); UI: en-US Calc: threaded Perhaps there is something to the way the combobox is created/named? Or maybe the underlying bug was fixed in the meantime.
Couldn't find this buggy behavior here for any version since LO 6.1. Older versions won't run with my databases. Tested with OpenSUSE 15.3 64bit rpm Linux. But when looking at comment 1 it should be a buggy behavior in LO 6.3 also. An example would help to see if the bug still appears.