In the release notes to 4.3 (https://wiki.documentfoundation.org/ReleaseNotes/4.3#Relative_text_frame_anchoring_improvements) the new feature of being able to assign sizes for text frames (and images) relative to the full page. This works if the image is anchored to the paragraph, but produces nonsense if the image is anchored to the page at the same time. To reproduce: 1. Open a blank writer document 2. Insert an image from file which is supposed to serve as a full page image. (For this test it need not exactly match the page aspect ratio.) 3. Double-click the image to edit the image properties. 4. Make sure "Keep aspect ratio" is checked. 5. Check Width "Relative to" and select "Whole page". 6. Check the anchor to be "On the page". 7. Klick OK to close the dialog. Expected result: - Image fills the page almost completely Actual result: - Image seems to disappear, actually it shrinks to a dot at the top center of the page. Want some more fun? 8. Right-click this (still selected) dot and bring up the dialog again. 9. Change the width value to 95% (of the page) and close the dialog with OK. New result: Image is completely disappeared. Note: - You get exactly the same result if you do it in two steps. First scale the image to 100% of the page width and close the dialog. This will the so far expected result. If you then reopen the dialog and switch to "Anchor to page", the image will shrink to a dot. -> Bug (P.S. I am using the German version, so option names might differ for you.) Operating System: Windows 7 Version: 4.3.0.1 rc
Created attachment 101427 [details] Book with image supposed to cover full page Simple test attached
I should add that frames inserted into the page act similarly strange when scaled and anchored relative to the page at the same time.
Confirmed in Linux Mint with 4.3. CCed Miklos as he implemented the new feature.
I see the same problem, when switching to "relative to page" from "relative to paragraph. The problem is still in Version: 4.4.0.0.alpha1+ Build ID: b167d1127e1579468a74c4414e7f4f33d9d24122 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-11-02_03:04:44 See bug 75060 and its attachment.
** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
The option width or height "relative to page" is still broken for images anchored to page. I see the error still in Version: 6.0.1.1 (x64) Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: CL
(In reply to Yousuf Philips (jay) (retired) from comment #3) > CCed Miklos as he implemented the new feature... in a series of commit leading up to https://cgit.freedesktop.org/libreoffice/core/commit/?id=1188866c1f0eb087a7e9b09bd9628f9c916feb68
proposed fix at https://gerrit.libreoffice.org/50034
Justin Luth committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=cffecd3c8d2d6b34726b8820468fadef93dd553d tdf#80282 swpagerelsize: corner case frame size max It will be available in 6.1.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.