Context: in Calc of LO 3.4.3 on WinXP Pro The cell range L155:AA155 contains empty cells. The cells on either end of that range are filled with numbers. The cell above L155 contains a formula. In fact all the cells in the row above (cells ...L154:AA156...) contain either a formula or a value. The task is to copy the formula from L154 to L155, make an edit, extend the range from L155 to AA155, Edit | Fill Right. The keystokes: In L154: Ctrl+C Down Arrow: moves to L155 Ctrl+V: paste Esc: terminate the "dotted border" focus on L154 F2: make the small edit Enter: terminate the edit Ctrl+Shift+RightArrow: SHOULD extend to AB156 where it finds the next filled cell in the row. ~~~~~~~~~~~~~~~~~~~~~: ACTUALLY extends selection to a large portion of column L. I originally thought that the faulty extension was to the entire column L. Mr. Stephan Zeitsman of the User's Help forum subsequently observed: "I just tried your example (after I posted my reply). I find that the selection is actually extended to K1:L155, which means it selects column K and column L (but not the entire column, only up to row 155). This is very strange behaviour, as it actually extends the selection to the *left*, although I pressed Ctrl + Shift + RightArrow." Workaround start as above until: F2: make the small edit Enter: terminate the edit RightArrow (once): shift focus from L155 to M155 LeftArrow (once): shift focus from M155 to L155 Ctrl+Shift+RightArrow: SHOULD and DOES extend to AB156 where it finds the next filled cell in the row. I use the M$ Natural Keyboard. The defective behavior results using either of the possible keys for "RightArrow": the 4-keypad "compass set" or the NumberPad (NumLock off). Mr. Stephan Zeitsman suggested I examine these two existing bugs: https://bugs.freedesktop.org/show_bug.cgi?id=39212 https://bugs.freedesktop.org/show_bug.cgi?id=37230 I slogged through those two. I think my issue is different. I am in no way attempting or expecting my keystroke sequence to intelligently (or foolishly) emulate any behavior I have ever used in M$ Excel. So I respectfully report here. -- David S. Crampton
Thanks for bugreport Please, attach spreadsheet that demonstrates this problem (where I can do described experiments)
Sasha, I have been away for a month. At this time I cannot spend more time on this bug report. I did a lot of detailed writing on it in my first submission. The problem still exists in build 402. Others have also reported it or similar. It was not so much spreadsheet specific as I recalled. Sorry I can't contribute more at this time. David -----Original Message----- From: bugzilla-daemon <bugzilla-daemon@freedesktop.org> To: dcramptond <dcramptond@netscape.net> Sent: Thu, Apr 19, 2012 2:46 am Subject: [Bug 42535] Editing UI: Ctrl+Shift-RightArrow faulty extension result https://bugs.freedesktop.org/show_bug.cgi?id=42535 sasha.libreoffice@gmail.com changed: What |Removed |Added --------------------------------------------------------------------------- CC| |sasha.libreoffice@gmail.com --- Comment #1 from sasha.libreoffice@gmail.com 2012-04-19 02:45:57 PDT --- hanks for bugreport lease, attach spreadsheet that demonstrates this problem (where I can do escribed experiments)
Dear Bug Submitter, Please read the entire message in its entirety before continuing - also please respond directly to FDO when replying - do not reply via email. 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
Bug Guys, In my original submittal, I gave a very precise keystroke sequence that produced the aberrant selection. I don't understand what more you might need. I see the same (or very similar) behavior in more recent v3.6.6.2. I just don't have the time nor the focus to revisit that keystroke sequence. If the bug falls off your list so be it. David -----Original Message----- From: bugzilla-daemon <bugzilla-daemon@freedesktop.org> To: dcramptond <dcramptond@netscape.net> Sent: Wed, Jul 17, 2013 11:15 pm Subject: [Bug 42535] Editing UI: Ctrl+Shift-RightArrow faulty extension result " QA Administrators changed bug 42535 What Removed Added QA Contact qa-admin@libreoffice.org Comment # 3 on bug 42535 from " QA Administrators Dear Bug Submitter, Please read the entire message in its entirety before continuing - also please respond directly to FDO when replying - do not reply via email. 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 You are receiving this mail because: You reported the bug.
Created attachment 82931 [details] Test document with steps to reproduce inside
Thanks for reply. Sorry for inconvenience. I have attached needed document. Reproduced problem in 4.1.0 on Fedora (RFR) 64 bit
*** Bug 78534 has been marked as a duplicate of this bug. ***
*** Bug 62436 has been marked as a duplicate of this bug. ***
As described in bug 62436, this bug seems to stem from all "move to block margin" operations immediately following a paste being wonky. Essentially, immediately after you paste into a cell, your next select/move to block margin operation(ctrl+arrow or ctrl+shift+arrow) will be erroneously based from cell A1 instead of the real cursor cell. My test: 1. Start a new spreadsheet 2. Insert a number in A10 3. Select any cell (C15 in this case) 4. Copy (Ctrl-C) 5. Paste into same cell (Ctrl-V) 6. Ctrl+shift+down Expected: We were in C15 when we performed the select to block margin action, so ctrl+shift+down should select the range C15:C1048576 Actual: Selects range A10:C15. This is because it selects from the cursor cell C15 to the cell ctrl+shift+down'd from A1. Since in step 2 we inserted a number into A10, it selects the range A10:C15.
The original report is very confusing and describes a special case of an issue I've run into several times within just a few hours of using LibreOffice. Simply put: after a Cut/Paste/Delete operation, keyboard navigation is utterly broken. Now, I don't know who LibreOffice tries to cater to, but I'm amazed this kind of bug can exist for years. Advanced users need keyboard navigation to work! Allow me to summarize the research: * After Paste, if you try to modify the selection using Shift+Up/Down/Left/Right, the other end of the selection will unexpectedly jump to A1 (bug 57008, bug 68703, bug 87388). * After Paste, if you try to modify the selection using Shift+Cmd+Down or Shift+Cmd+Right, the other end of the selection will unexpectedly jump to column A or row 1 (this bug). It may be more complicated than that — I haven't tested this extensively. * After Paste, if you try to move to the next (but not previous) value in the column/row by hitting Cmd+arrow, the movement will overshoot by an amount that's based on the original cursor location (bug 62436). * After Cut/Delete, if you try to move to the next *or* previous value in the column/row by hitting Cmd+arrow, the movement will over-/undershoot by an amount that's based on the size and direction of the prior selection (bug 95730). It has been conjectured that all of these are in fact the one and the same bug. Perhaps. But it should be noted that the "Move to block margin" command can miscalculate the coordinates in three different ways depending on whether you're simultenously modifying a selection and whether the previous operation was Paste or Cut/Delete. Also, when the selection is being modified, even basic Up/Down/Left/Right navigation is enough to trigger the jump to A1, so it's not just about "Move to block margin". However, if these are indeed various manifestations of the same faulty arithmetic, then fixing it would likely be fairly easy and yield a huge payoff for the effort in terms of usability. For now, I'm going back to the increasingly obsolete OpenOffice because it's just more usable. I have tested recent and 3.3.0 versions of both LibreOffice and OpenOffice. LibreOffice has always had this bug, OpenOffice never.
** 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
Bug still reproducibly with: Version: 5.2.3.2 Build-ID: 1:5.2.3~rc2-0ubuntu1~trusty1 CPU-Threads: 8; BS-Version: Linux 4.4; UI-Render: Standard; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group
** 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
In 5.3.7.2 this bug continues as originally described.
Dear David, 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
Just tested with version 6.0.7.3 in Ubuntu and the bug is still present as described above. -- LibreOffice Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.10
*** Bug 132936 has been marked as a duplicate of this bug. ***
Dear David, 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
*** This bug has been marked as a duplicate of bug 146994 ***
I marked it as a dupe of bug 146994; but *maybe* it's rather bug 95730. Please text with 7.4+; if reproducible, then it should be set NEW, and bug 95730 marked as a duplicate of this.