Created attachment 114458 [details] Ellipse anchor bug on page 8 In attached file, p.8, when drawing a red ellipse on top of the image on top of the page, it jumps to the footer area of the previous page and can no longer be selected. Also impossible to draw an ellipse on top of the image except in anchor mode "page" (but I want it to move with the image). To reproduce: - open attached file - scroll to page 8 - draw an ellipse on top of the image on top of the page Observed behavior: ellipse jumps to footer area of previous page Expected behavior: ellipse stays on top of image, or jumps to page area (not footer area) of page above Alternatively: - draw the ellipse in the text area below the upper image, it will stay in place - drag the ellipse unto the image above, it will again jump to the footer area of the previous page Changing anchor mode of the ellipse to "to Paragraph", "to Character" or "as character" does not change anything. "To Page" works, but is not desired (ellipse has to move together with underlying image). The same setup (ellipse on top of image) does works on the second image on the same page.
Reproducible with LO 4.4.1.2, Win 8.1
Also reproducible on Linux in LO 3.3.0 -> Version: Inherited from OOo -> Platform: All
** 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.5 or 5.1.2 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: 2016-04-16
** 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.2.7 or 5.3.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-20170522
Reproduced with LibreOffice Writer 5.3.2.2 Windows 10 Pro build 1703. Same bug behavior.
** 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
Dear Bart, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 180832 [details] demonstration of red ellipse with image at top of page (In reply to Bart from comment #0) > - open attached file > - scroll to page 8 > - draw an ellipse on top of the image on top of the page See attachment for an example. Note: (a) the red ellipse does not appear (cannot explain why!), but use Navigator, and Drawing Objects, where you should see "Red ellipse anchored to character"). If you double-click on that name in Navigator, then you will see the shape become highlighted over the image (the "Update Software" part) (and if you drag one of the corners of the shape, then you will see that it appears as a red ellipse. And if you drag the shape off of the image, then it appears. I tried changing the wrap, arrangment and size, without success (b) I could not reproduce this problem of the disappearing ellipse starting with a new document, using an image anchored "as character" and then placing shapes on top of that image, using "to character" anchors (c) I also tested that if the image moves to the previous page (e.g., because text was deleted), then the red ellipse follows the image -- as you wanted. Your comments show that you appreciate that the anchor affects where the shape appears. This is why "to paragraph" anchor places the ellipse on the previous page. And if the "to character" anchor was not placed on the same page as the image, then the shape will be placed on the page where the "to character" anchor is located -- as you reported. The attached version has placed the "to character" anchor on the same page as the image (just after the image, you will see it in the upper right corner when the ellipse is selected). > The same setup (ellipse on top of image) does works on the second image on > the same page. This is because the paragraph (to which it is anchored) and the image are on the same page. If the text was on one page and the image on the next page, then you would observe a similar problem. in my opinion, this ticket is "NOTABUG". What do you think?
Created attachment 180835 [details] demonstration of red ellipse with image at top of page Attached is the correct version of the demonstration (i.e., with the right positioning controls to keep the ellipse positioned correctly to the image if the image is moved to the previous page). Curiously, if you test this, then the red ellipse does get shown when the image is moved to the previous page.