v2 tdf#134951 docxexport GUI: don't lose postponed comment
A previous patch handled ooxmlexport's unit test failure.
But saving interactively writes the nodes in a different
order, and thus the flys process differently.
The comment was still lost/moving into the textbox
when manually testing.
So, just make sure that comments are written out before
a call to OutFlys().
There is one other place where OutFlys is called that
I didn't cover here. As a !bTextAtr, it doesn't seem
likely to need it, plus I don't want to modify ANYTHING
here without a proof document.
Change-Id: Iaf3d19bd8d8f6744b9fea1c8686e59612c0a7ff8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128732
Tested-by: Justin Luth <jluth@mail.com>
Reviewed-by: Justin Luth <jluth@mail.com>
diff --git a/sw/source/filter/ww8/wrtw8nds.cxx b/sw/source/filter/ww8/wrtw8nds.cxx
index 6a84f77..a1409a6 100644
--- a/sw/source/filter/ww8/wrtw8nds.cxx
+++ b/sw/source/filter/ww8/wrtw8nds.cxx
@@ -2720,6 +2720,8 @@ void MSWordExportBase::OutputTextNode( SwTextNode& rNode )
if (bTextAtr || bAttrWithRange || bIncludeEndOfParaCRInRedlineProperties)
{
AttrOutput().WritePostitFieldReference();
// insert final graphic anchors if any before CR
nStateOfFlyFrame = aAttrIter.OutFlys( nEnd );
// insert final bookmarks if any before CR and after flys
