Created attachment 146593 [details] Sample ODT Open the attached document with a long single paragraph, and a shape anchored to the paragraph. Try to drag the shape to the next page. => A couple of things might happen: - the chape can disappear completely, - the shape might disappear, but the area and selection outline remains, - the shape might fail to leave the first page (versions < 6.1). While the sample is extreme as it contains a single paragraph, the behavior is the same with a paragraph spilling over to the next page. Observed using versions 6.2.0.0.alpha1+ (397dd8a5f7694540f31f32759c2c915d63506ccd), 3.3.0 / Windows 7.
Sounds a lot like bug 120839
(In reply to Telesto from comment #1) > Sounds a lot like bug 120839 There are similarities, perhaps the changed behavior is related to the same commit, but this never worked properly.
Bug confirmed. Using the attached file. On page 3 top bug confirmed. Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded
(In reply to Chen yu an from comment #3) > Bug confirmed. > > Version: 6.3.0.0.alpha0+ (x64) > Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 > CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; > TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 > Locale: zh-TW (zh_TW); UI-Language: en-US > Calc: threaded
I can confirm that the bug is present in Version: 6.0.6.2 Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU threads: 2; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group
Dear Aron Budea, 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 Aron Budea, 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
Still in LO Version: 7.4.0.0.alpha0+ (ba7db98cca3d8516697c94ef0d6af27db9e1655e) / Ubuntu.
*** Bug 150484 has been marked as a duplicate of this bug. ***
Help states clearly: "Objects can only be positioned on the page where their anchor is located." https://help.libreoffice.org/7.4/en-GB/text/swriter/guide/anchor_object.html?&DbPAR=writer&System=WIN So actual behaviour is the expected one. So for me NOTABUG. Aron feel free to reopen it as enhancement request or file a new report as enhancement, if you think, we should change current behaviour. Workaround: Change anchor to page.
(In reply to Dieter from comment #10) > Help states clearly: "Objects can only be positioned on the page where their > anchor is located." > https://help.libreoffice.org/7.4/en-GB/text/swriter/guide/anchor_object. > html?&DbPAR=writer&System=WIN > > So actual behaviour is the expected one. So for me NOTABUG. Aron feel free > to reopen it as enhancement request or file a new report as enhancement, if > you think, we should change current behaviour. Thanks for the comment Dieter! For the record, that addition to the help was made fairly recently in 7.4 for bug 149353, and it rather seems to me a comment to inform users of this limitation than the actual expected behavior (at least, concerning the steps in this report). I'd maintain that this is a bug from the user's perspective, but I can also understand this is currently a limitation, so switching this from bug to enhancement is fine.
(In reply to Aron Budea from comment #11) > so switching this from bug to > enhancement is fine. I've also changed bug summary to make enhancement request more visible. Regina, are there are any limitations from odf-specification? cc: Regina Henschel
The ODF specification does not mention such case. From the existing text I see nothing, that would limit it. But from a practical point of view, I see big problems. The layout algorithm is already very fragile, and Word has the same behavior. So changes are extremely vulnerable to regressions.