Hi, Steps to reproduce in: 1- Activate a cell by mouse double click to enter edit mode 2- Click "=" to start formula syntax, then click the arrow keys to select other cells to form a formula for example (=A3*B5) Current situation: Arrow keys doesn't work, only selection with mouse cursor&click is possible. Expected situation: Arrow keys should be working. PS: sorry for the bad title. Best regards, Zeki
Reproducible with Version: 5.1.0.0.alpha1+ Build ID: b2363e98af7b0281279617e43b8fec5b898b9120 TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-08-26_00:57:35 Works OK in LibreOffice 3.5.0 ,Build ID: d6cde02 -> regression
(In reply to raal from comment #1) > Reproducible with Version: 5.1.0.0.alpha1+ > Build ID: b2363e98af7b0281279617e43b8fec5b898b9120 > TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: > 2015-08-26_00:57:35 > > Works OK in LibreOffice 3.5.0 ,Build ID: d6cde02 -> regression I planned to bibisect this. However I did not find a single version where moving to another cell using the keyboard worked after double-clicking into a cell and then pressing "=". I also tried with OpenOffice.org 3.3.0 (Build:9567) and LibreOffice 3.5.0rc3 (Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735) from the "bibisect-releases" repository. However, in all versions I looked at, moving to another worked fine when selecting the first cell using a single mouse click, i.e.: 1. Activate a cell by SINGLE mouse click 2. Click "=" to start formula syntax, then click the arrow keys to select other cells to form a formula for example (=A3*B5) @raal: Could you possibly verify again whether it actually works in LibreOffice 3.5 after using a DOUBLE mouse click to select the first cell. In general, I am not certain whether the described behaviour is actually a bug or whether the behaviour is OK as it is (I do not feel able to judge this...).
Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit]
I tested all the way back to 3.3 and the same behavior exists.
** 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
Dear Zeki Bildirici, 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 Zeki Bildirici, 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
If cell editing it is started with F2, than =, arrows can be used. When cell editing it is started with double click, then =, arrows can NOT be used. Retested with Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 3070091c9eafc964ebb3f53d3b44124b40571fd8 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded