Bug Hunting Session
Bug 104823 - For Word 2016 Content Controls Placeholder Text is Being Displayed Instead of Text from XML
Summary: For Word 2016 Content Controls Placeholder Text is Being Displayed Instead of...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:docx
Depends on:
Blocks: DOCX
  Show dependency treegraph
Reported: 2016-12-20 20:32 UTC by Andreas Hofmann
Modified: 2018-01-12 03:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

.docx file with Content Control (21.83 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2016-12-20 20:32 UTC, Andreas Hofmann

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Hofmann 2016-12-20 20:32:03 UTC
Created attachment 129827 [details]
.docx file with Content Control

This issue was first brought up by Timur Sattarov on Dec 1, 2015, but then deemed a duplicate of bug 50097:

When reading docx file that contains Word Content Controls, MS Word shows "data from databinding", but Libreoffice shows only the placeholder text.

Note: This is NOT a duplicate of bug 50097 as this issue is about the wrong text being displayed when a .docx file is opened in Writer. Instead of resolving the XML file and displaying the text from the XML file (like Word 2016 does), Write just displays the placeholder text.
Comment 1 Buovjaga 2016-12-31 15:15:49 UTC

Arch Linux 64-bit, KDE Plasma 5
Build ID: fc0d4e6bc43d5f982452df07930f5ecf5927ad22
CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on December 31st 2016
Comment 2 QA Administrators 2018-01-12 03:30:47 UTC
** Please read this message in its entirety before responding **

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 http://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