In some cases the dropdown/listbox type content controls are opened as legacy fields. This was added in bug 134043 in 7.1, to cover a special "legacy field in odt" -> docx -> Writer use case. Export already used sdt controls. However this behavior was largely removed in 7.4 with commit: https://git.libreoffice.org/core/+/24417d8c3c9e1c619936e85fa7a20481a24e3530 author Miklos Vajna <vmiklos@collabora.com> Wed May 11 08:17:32 2022 +0200 committer Miklos Vajna <vmiklos@collabora.com> Wed May 11 09:25:27 2022 +0200 sw content controls, drop-down: add DOCX import For example if the example file from bug 134043 attachment 162064 [details] is saved in 7.1, then reopened in 7.4, the fields open as proper content controls and not as legacy fields anymore. However there are still corner cases where the old hack is triggered. One such case is the unit test example file sw/qa/extras/ooxmlexport/data/combobox-control.docx which was added in bug 134043 and contains only a single dropdown content control. The attachment is a reproduction of this file to show it's nothing special. Another case is when this content control is inside a table. I'm not sure why are these special, but overall I think this SdtHelper::createDropDownControl() method has outlived its usefulness. Also its behavior can be modified with the officecfg::Office::Writer::Filter::Import::DOCX::ImportComboBoxAsDropDown config key: turning it off makes the content controls import as UNO form control, which existed before the above hack to turn them into fields was added - another obsolete approach now that we have viable content control implementation. 1. Open attached document -> Check in the Navigator that it contains a field 2. Go to Options - Advanced - Expert configuration 3. Search for the key ImportComboBoxAsDropDown and turn it off 4. Reload the document -> Check in the Navigator that it no longer contains a field, but there is a form control The same steps apply for the second example file. Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 43967453e15e1d054972a7586cfef8f8e0866270 CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded
Created attachment 191295 [details] The example file in Word 2016 and Writer master
Created attachment 191296 [details] The second example file with problematic dropdown inside table Note that the very first dropdown is the same as in the other file, which is now a normal content control.
Created attachment 191297 [details] The first example file somehow this got lost...
Created attachment 191298 [details] Screenshot of the second document in Word and Writer
I confirm for both axample files with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 40617d867346956588ac023511f31210107217f4 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded
Dear Gabor Kelemen (allotropia), 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