Bug 119986

Summary: FILESAVE DOCX The MatchEntry property of the list box ActiveX control is incorrectly saved
Product: LibreOffice Reporter: Gabor Kelemen (allotropia) <kelemeng>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: normal CC: libreoffice, raal, xiscofauli, zolnaitamas2000
Priority: medium Keywords: filter:docx
Version: 6.0.0.0.alpha0+   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 104523    
Attachments: Example file from Word with two list boxes
The original file saved by Writer.
Screenshot of the original and exported document side by side in Word.

Description Gabor Kelemen (allotropia) 2018-09-19 16:26:37 UTC 
Created attachment 145027 [details]
Example file from Word with two list boxes

The MatchEntry property of the list box ActiveX control is incorrectly exported in DOCX documents created with Microsoft Word 2010.

Steps to reproduce:

    1. Create a new document in Microsoft Word 2010.
    2. On the Developer tab, in the Controls group, click Design Mode.
    3. Insert a list box ActiveX control.
    4. Right-click the control, and click Properties.
    5. Set the MatchEntry property: 0 – fmMatcEntryFirstLetter.
    6. Or set the MatchEntry property: 1 – fmMatcEntryComplete.
    7. Save the file as DOCX.
    8. Open the same file in LibreOffice Writer.
    9. Select File and Save As.
    10. Name the file.
    11. Open the exported file in Microsoft Word
    12. On the Developer tab, in the Controls group, click Design Mode.
    13. Right-click the control, and click Properties.

Actual results:
The value of the MatchEntry property is 2 - fmMatchEntryNone.

Expected results:
The value of the MatchEntry property shouldn’t change.

LibreOffice details:
Version: 6.2.0.0.alpha0+
Build ID: efe119aaa50e9f532b3fac1ef153469c80f24b80
CPU threads: 4; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-09-10_00:02:50
Locale: en-US (hu_HU); Calc: threaded
Comment 1 Gabor Kelemen (allotropia) 2018-09-19 16:48:42 UTC 
Created attachment 145028 [details]
The original file saved by Writer.
Comment 2 Gabor Kelemen (allotropia) 2018-09-19 16:49:02 UTC 
Created attachment 145029 [details]
Screenshot of the original and exported document side by side in Word.
Comment 3 raal 2018-10-15 12:39:47 UTC 
confirm. Version: 6.2.0.0.alpha0+
Build ID: 425af6845ebe066c950b0b63f50563e067485f3e
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win;
Comment 4 QA Administrators 2019-10-17 02:37:00 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-10-17 03:54:29 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-10-18 03:14:52 UTC 
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