sw/qa/extras/ooxmlexport/ooxmlexport17.cxx | 2 ++ 1 file changed, 2 insertions(+)
New commits: commit 2315f0fe9ef1f94634d1a8944203b234170becf7 Author: Justin Luth <[email protected]> AuthorDate: Mon Jan 19 16:21:05 2026 -0500 Commit: Justin Luth <[email protected]> CommitDate: Tue Jan 20 02:40:19 2026 +0100 tdf#170322 docx export: explain why unit test checks for <w:text/> This unit test nicely has 4 examples of plain-text content controls. The first three have an explicit <w:text/> in them that we obviously need to round-trip. However, the last one has no type identifier, and NORMALLY that would mean it is a richText control instead of a plainText control. Yet, MS Word considers it to be a plainText control, apparently because it has a dataBinding. So add wording to the unit test to confirm that this fourth one really is appropriately round-tripped as an explicit <w:text/> plainText control. Change-Id: Ib2aa59cd6523ef318c2596805dbc534971ab61f7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/197612 Tested-by: Jenkins Reviewed-by: Justin Luth <[email protected]> diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx index 3a42e7e3890d..bbb5aaffa922 100644 --- a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx +++ b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx @@ -923,6 +923,8 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf81507) // Ensure that we have <w:text/> assertXPath(pXmlDoc, "/w:document/w:body/w:p[3]/w:sdt/w:sdtPr/w:text"); + // (related tdf#170322) The last one did NOT import with a <w:text/> type identifier, + // however it IS plainText in MS Word - apparently because it has a dataBinding assertXPath(pXmlDoc, "/w:document/w:body/w:p[4]/w:sdt/w:sdtPr/w:text"); }
