Created attachment 84483 [details] one .odt file with sample text and instructions to see the bug. Problem description: Using frames in a large document together with footnotes, and they cannot be always positioned where one wants. Steps to reproduce: 1. create small frames with notes at right side of page. 2. document has footnotes with references at bottom of each page 3. click on side of frame, so it is selected. 4. Use up arrow key and down arrow keys Current behavior: As you click up arrow, the frame moves up steadily until the first paragraph on page, when it suddenly jumps to the previous page and lans in the "footer" area of that page. Try to press down arrow again, and it doesn't budge at all. If the frame is too small, and the frame totally below the footnote line, and the cursor focused onto the main text area, one can no longer move the frame at all. (I have to "control+enter" after the previous paragraph, in order to force it back to the follow on page). Expected behavior: I expect the up arrow to move the frame up to any place on the page until I reach the top, and then for it to jump to the previous page. I also expect the down arrow to move it back to the page it came from. Ther is another connected bug, when a frame is deleted from within the footnote area, I am automatically taken back to the very first page of the document. Operating System: Windows 7 Version: 4.1.0.4 release
To move a frame from a page to another, it is less expensive to use the mouse or the cut-and-paste instead of hitting several times on the arrow keys. That said, after several experiences, I think that the ability to move a frame using up and down arrow keys seems to have not been designed to work outside the current page. I tend to close this bug report as NotABug. Any advice? Best regards. JBF
I'm really not sure what you mean by "less expensive". If I use the cut and paste, the frame does not get placed exactly where I tell it to get pasted. It's quite difficult, for example to place a frame directly between 2 paragraphs "without" using the arrow keys. In any case, the behaviour is erratic, and if the arrow key moves it up to the previous page (which it does!), surely it would just make logical sense that it would move it back down again, (which it doesn't). Also the fact that the frame can get stuck in the footer area is quite annoying and surely merits being listed as a bug rather than an extremely badly thought through feature. Also, there is currently no way to place a frame within a paragraph that started on the previous page. Try featuring such frames in your own writing, I think you will soon realise that the degree of control is minimal and that this needs addressing.
Dear Bug Submitter, Please read the entire message before proceeding. This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Added whiteboard NeedAdvice because of my comment #1 and set the status back to unconfirmed. Best regards. JBF
I confirm "arrow keys" issue on Win7x64 using LibO 4.3.2.2 I set status to NEW and let's see what other people from the QA team thinks about this: a BUG or NOTABUG ?
Thanks for reopening this Tommy.. This "bug" is still present and demonstrable in the latest version of LO, via the attachment I uploaded here earlier.. It is quite frustrating if one uses frames a lot (which I do)..
@mango do not change version field to latest version you see the bug. it should indicate firts version the issue apperared. after more tests I can tell this bug is inherited from OOo (affects OOo 3.3.0, LibO 3.3.3 and AOO 4.1.0)
(In reply to tommy27 from comment #7) > @mango > do not change version field to latest version you see the bug. it should > indicate firts version the issue apperared. after more tests I can tell this > bug is inherited from OOo (affects OOo 3.3.0, LibO 3.3.3 and AOO 4.1.0) ok.. sorry about that..
** 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.1 or preferably 5.0.2.2 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-10-14
This bug definitely continues with version 5.0.1.2, as far as I can see there has been no change, and it's still as irritating as ever. It works exactly the same way in the lastest Open Office version too. I'm using windows 10. cheers, mango.
Migrating Whiteboard tags to Keywords: (needAdvice)
Does anyone know if this bug will be fixed in the up-and-coming version 5.1?
very disappointed to see that this bug is still not fixed in version 5.1…
'needsConfirmationAdvise' is only used for unconfirmed bugs. Removing it from this bug. [NinjaEdit]
Is there any chance that this bug will be fixed in the up-and-coming version 5.3? It's been over three years since I reported this bug, which has been present since the very beginning of LibreOffice.. it really would be great to know that this bug is not being completely ignored, as it is still something which I find restricts my usage of this otherwise fantastic office suite.
I'm very sad to see that this bug is still not fixed in version 5.3… Surely it is more important to fix bugs in a program before adding new features? This issue has been around since the dawn of libreoffice/openoffice and is still present, and still very annoying. It has been well over three years since I first reported it too.. It would be much appreciated if some kind soul could at least acknowledge that this bug is being worked on, or low prioritized on a long list of bugs that need fixing?
I confirm the impossibility to move the frame in the described manner with arrow keys. I also discovered that you can't move the frame with the mouse to a position within the paragraph that started at the page before. It's only possible to anchor it to the next paragraph. Maybe that behavior for arrow keys and mouse has the same cause. Version: 5.3.0.3 Build ID: 1:5.3.0~rc3-0ubuntu1~trusty1.1 CPU Threads: 2; OS Version: Linux 3.13; UI Render: default; VCL: gtk2; Layout Engine: new; Locale: de-AT (de_DE.UTF-8); Calc: group Jumping when deleting a frame is also covered by Bug 101932. That bug is newer as this one but to respect the "one report per bug" rule I would suggest to handle the jumping issue there. mango: I think it's unlikely that this bug will be fixed in the near future unless you will personally find a developer who is willing to work on it. There are a thousand times more issues than developers and the priority is not high - see https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Priority#Priority_Levels
** 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
This issue is still present within libreoffice writer.. Version: 6.0.4.2 (x64) Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: en-AU (en_AU); Calc: group I believe I've already marked someplace that the issue has been around since the beginning of libreoffice, and is still present with openoffce too..
Dear mango wodzak, 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
Yes.. bug is still annoyingly present in 6.2.4.2 ..
Bug is still present in v6.3 .. only now one can no longer double click on a frame edge to open the properties dialogue, and aligning a frame using the align buttons causes separation of text from the frame.. Frames seem to work differently in 6.3, someone is tweaking things there, but doesn't look like they've improved things at all..
Dear mango wodzak, 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
Not yet fixed.... the bug is still firmly present. Version: 7.2.1.2 (x64) Build: 87b77fad49947c1441b67c559 Environment: CPU Threads 12; OS; Windows 10.0 Build 19403 User Interface: UI render: Skia/Raster; VCL; win Locale: en-AU (en-AU); UI en-GB Misc: Calc: threaded
(In reply to QA Administrators from comment #25) > Dear mango wodzak, > > 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 yes.. already replied.. Not yet fixed.... the bug is still firmly present. Version: 7.2.1.2 (x64) Build: 87b77fad49947c1441b67c559 Environment: CPU Threads 12; OS; Windows 10.0 Build 19403 User Interface: UI render: Skia/Raster; VCL; win Locale: en-AU (en-AU); UI en-GB Misc: Calc: threaded
This bug is still present in the latest version of LO : Version: 7.5.0.3 (X86_64) / LibreOffice Community Build: c21113d003cd3efa8c53188764377a8272d9d6de Environment: CPU threads: 12; OS: Windows 10.0 Build 22621 User Interface: UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Misc: Calc threaded