Problem description: When you have created a document with formulas and images, you may want to insert a paragraph (text processing programs are done for that). Unfortunately, when you add your text, images are often moved down and go out of the print zone. So, after you have inserted your new text, you have to manually move the images and formulas so that they go back to the print zone. It is a quite big loss of time for big documents with no page return. Current behavior: Images are moved and my go out of the defined print zone. Expected behavior: If images should be moved with the paragraph they are linked to, they should stay in the print zone. Platform (if different from the browser): Every platform Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0
I actually am positive that I read the polar opposite on another bug report (where a user got irritated that images couldn't go outside of print zone) but I'll have to dig around to find that bug. As for your suggestion, so if an image moves down and it forces it to go out of the print zone, it would then just end up on the next page? I'm not sure how that saves much time if you still have to edit the image to get it back on the original page. Many thanks for clarifying
Most of the time, the image should stay on the current page but should be automatically blocked by the print zone (it goes up in the paragraph). The basic idea is : as the "out of the print zone" should be empty, there is no reason why the user would want the images to automatically go out of the print zone. On the contrary, a user should always be able to move an image out of the print zone manually (ie drag & drop). The image should go to the next page only if the whole paragraph jumps to the next page or if there is really no place left for the image on the current page.
Created attachment 72066 [details] Exemple document If you add some extra lines in the paragraph "Nothing", the formula and the OLE object will be moved out of the print zone. I expect most users don't want this.
I agree with Colin that moving the graphic objects out of printing range, isn't a great idea. Imo the objects should be moved to the next page directly instead first going out of print range. To reproduce: as Colin writes, open test document and enter additional lines after "nothing" text. Tested with LO Version: 4.3.0.0.alpha0+ Build ID: 73342dbb82ba074d01962359dac50fb2aa36cbeb TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2013-11-22_07:09:14 Setting to NEW.
** 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 (4.4.1 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 *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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
The bug is still present with version 4.2.7.2 (Ubunut 14.04 build, amd64)
** 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.5 or 5.2.1 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-20160920
Joel: Did you mean Bug 92745 - Ability to drag image partially off the page ?
(In reply to Thomas Lendo from comment #8) > Joel: Did you mean Bug 92745 - Ability to drag image partially off the page ? He was likely talking about bug 50206, which bug 92745 is a dupe of. But the issue here is that frames, images, shapes, OLEs are going into the page margin as 'follow text flow' is disabled in the properties dialog, which users can enable if they dont like this default behaviour.