Fixed in LO 7.0 by commit 38e7e6f348df5d6b37d7e0051fd3b8c227db69e6
Author: Justin Luth on Tue Apr 14 17:39:36 2020 +0300
tdf#132094 doc: fix export of fill in wrap-through fly frames
This builds on commit 2f13dbac060ae6af7e25ad3eff675cc859cfb3ff
by Miklos Vajna on Fri Jun 15 08:49:46 2012 +0100
n#325936 fix ww8 export of fly frames with transparent bg
where he wisely and cautiously says
Regression from commit ed8b5f2d -- to be safe, reverted only
for fly frames in headers.
because for some unknown reason, way back in 2002, commit
ed8b5f2debac216243930aba0873e0d75de8d0dd forced all
frames to specify a background fill. Typically of
course this is white, and so who notices?
Well, you notice if your frame is transparent, and
now the area fill hides something that it is over top of.
Like for example a transparent image, where the text wraps
through the image.
At first I was going to just try and revert everything.
Then I decided it likely was a difference between how
LO and MSO handled stacking/overlapping things.
After that, I was going to just make an exception for
eShapeType == mso_sptPictureFrame, but that only seems
necessary if there is something underneath. If the something
is just a background, that is handled anyway, so really
it would only be other shapes or (most importantly) text,
so the safest thing is testing wrap through, which there was
already a pre-defined variable to reuse
(and fix the spelling).
*** This bug has been marked as a duplicate of bug 132094 ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873287
Title:
[Upstream] Writer Picture Background No Fill does not persist saving
to .doc
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/873287/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
