Created attachment 43690 [details] image with layer Here is gif picture. When I open it in Gimp I see: Size of whole image 580 × 387 pixels. Size of layer 575 x 227 pixels. When I insert it in office it output on screen, it outputs only layer, but not whole image. HTML document becomes corrupt. I tried it on Linux 64. Mozilla outputs whole image.
On windows 32 the same problem as on Linux 64.
Reproducued with LO 3.3.1 RC2 Ubuntu 10.04 x86.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced on LibO 3.5.0 beta 1
Created attachment 78678 [details] Libo 4.1.0.0 master with this gif
I can't see any problem with 4.1.0.0 master (didn't try 4.0).
On second screenshot I see that problem is still reproducible. Picture ends exactly beneath frames of text. But should be empty space beneath of frames. And hight of picture should be almost 2 times bigger. PS: this picture is generated by msWord by saving document as HTML. Pictures with this problem may be potentially very popular. And therefore problems is important. What is interesting: copy-pasting this picture from Firefox to LibreDraw pastes it with correct size, but with black background (because pastes as JPEG)
Ah ok, didn't see that it's bigger in height.
On pc Debian x86-64 with master sources updated today, I reproduce the problem. Michael: do you know who may help here? (eg by giving some code pointers?)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.