Steps: 1) Open Writer 2) Insert an image 3) Resize the image so its not taking up the entire width of the page 4) Format > Image... 5) Set a border 6) Notice that rather than putting a border and spacing between the image and border, the image is shrunk to accomodate the border and spacing within the area of the image. Version: 4.5.0.0.alpha0+ Build ID: de145fb467f2a168261915d63b47d3cd3b03d732 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-03-15_09:51:29
*** Bug 90071 has been marked as a duplicate of this bug. ***
Reproducible with LO 4.4.1.2, Win 8.1
Thanks Andy for noticing that it submitted it twice. Bugzilla has been acting up lately.
So it seem this not only affects images, it also affects OLE objects like charts, and it also effects compatibility.
Created attachment 114855 [details] sample docx Attached is an example docx file, which when opened in LO results in the image being cropped to give place to the borders.
Kendy asked me to CC you on this. :D
Created attachment 128498 [details] imagePadding.odt - image with border and padding This is not inherited from OOo, but is a regression between 3.6 and 4.0 somewhere between bad commit b679a2a02180c017bd8b596fb2e4f283bad93b75 Author: Noel Grandin <noel@peralex.com> CommitDate: Wed Sep 5 15:46:55 2012 +0200 fdo#46808, Adapt reflection::CoreReflection UNO service to new style and good: commit 7dd6c0a8372810f48e6bee35a11ac4ad0432640b Author: Noel Grandin <noel@peralex.com> CommitDate: Mon Sep 3 15:55:05 2012 +0200 Remove some unnecessary includes from the IDL files and almost certainly due to this commit e598ab04476a32a08f18e8f0662fafa5f78f1a4a author Cédric Bosdonnat <cedric.bosdonnat.ooo@free.fr> 2012-09-04 10:59:52 n#775270: clip pictures instead of scaling they don't fit
proposed fix: https://gerrit.libreoffice.org/30585 tdf#90070 don't clip flys with borders
Justin Luth committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=d034f273cb24ebe4fde20ad9089ac11cccf316d0 tdf#90070 don't clip flys with borders It will be available in 5.3.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-5-2": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ab64ae2a828f4acd6d118abc14193c543d04b940&h=libreoffice-5-2 tdf#90070 don't clip flys with borders It will be available in 5.2.4. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Hi Justin, Your fix fixes the regression introduced in 4.0 relative to your attachment 128498 [details], but doesnt resolve the OOo inherited issue mentioned in the description or in attachment 114855 [details].
Created attachment 128848 [details] ImageBorder.doc: 2page MSO2003 doc testing image with border spacing It appears that Writer's scale-down-the-image-to-add-a-border is different from MSWord, which enlarges-the-frame-to-accommodate-the-border. (This test document drops down to one page in Word when the border is removed, but Writer just scales up the image to fill the empty space.) This doesn't seem to affect interoperability - both open the saved document identically. The patch in comment 9 addresses the cropping issue (where the image is cut off by the border) but not the avoid-scaling enhancement requested in the description. Removing myself from the bug along with any indicators that the bug has been fixed.
*** Bug 95475 has been marked as a duplicate of this bug. ***
still present in LibO 5.4.0.0.alpha0+ Build ID: 5bb5a9dacb84ec14f7148a5a5d9ba38b7e9f1039 CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-02-17_23:30:45 Locale: it-IT (it_IT); Calc: group
** 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 MassPing-UntouchedBug
The error still exists in Version: 6.2.0.0.alpha0+ (x64) Build ID: f7f2d03bd6f5aa5dcd0f7976b4a7f2db278c2f03 CPU threads: 8; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-05-25_05:00:28 Locale: de-DE (de_DE); Calc: CL The problem is, that the image is imported as Writer-image, but it needs to be a Draw-image for to get the same "border" as in docx. In fact it is not a border but a line.
The error exists too, if a border is added to an Writer-image. With the current implementation, the size would need to be increased by the 2 x border width.
I vote for WFM since adding a border to the outer space changes the text flow.
Would adding a setting whether to add the border inside, outside or centered be a reasonable compromise?
Lowering importance: Highest + Inherit from OOo doesn't make much sense at this point anymore...
Dear Yousuf Philips (jay) (retired), 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 https://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 MassPing-UntouchedBug
*** Bug 143632 has been marked as a duplicate of this bug. ***
*** Bug 142826 has been marked as a duplicate of this bug. ***
*** Bug 156778 has been marked as a duplicate of this bug. ***