Created attachment 115044 [details] Precedents continuous error Ctrl+[(Mark Precedents) Error When continuous use. The first time use Ctrl+[,it's OK,but if the precedents cells is a formule, and continuous press Ctrl+[,the precedents are error. Step to reproduce: 1. Set these formule: B3 =A2+B1 C3 =B2+C1 D3 =B3+C3 2. select D3. 3. press Ctrl+[, you can see Calc selects B3 and C3,that's OK. 4. press Ctrl+[, you can see Calc selects A2 and B1,it's Wrong, the right selects is A2 and B1 and B2 and C1. Another Error to reproduce: 1. Set these formule: B15 =A14+B13 C15 =C14+B15 2. select C15 3. press Ctrl+[, you can see Calc selects C14 and B15,that's OK. 4. press Ctrl+[, you can see Calc selects B13 and C12,it's wrong, the right selects is A14 and B13(I think) or None(Excel 2013 do). I have tests in Windows 7 SP1 and Fedora 21 x86_64 using LibreOffice 4.4.2.2 and 5.0.0.0. This bug is first put on LibreOffice Chinese Forum, http://www.libreofficechina.org/thread-851-1-1.html
Could not confirm problem. In the first case, the final selection was correctly A2 and B1 and B2 and C1 for me. In the second case, the final selection was correctly A14 and B13. My default shortcut for Track precedents is Shift-F9. Tested on: Win 7 Pro 64-bit Version: 5.0.0.0.alpha1+ (x64) Build ID: f3375fa07f27bd2ade519af3c07d69040d10eaa9 TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-22_23:38:50 Locale: fi_FI
I can confirm with Version: 5.0.0.0.alpha1+ Build ID: e9fbe1f7cd28de2a9da8089d89e903406165eb56 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-04-25_00:20:28
** 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.5 or 5.2.1 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-20160920
This bug is still reproducible in 版本：5.4.4.2 Build ID：5.4.4.2-4.fc27 CPU 线程：4; 操作系统：Linux 4.14; UI 渲染：默认; VCL: gtk3; 区域语言：zh-CN (zh_CN.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
Still reproducible in Version: 7.1.0.1.0+ Build ID: a88dbaf6a9076b546300f3c640ac38c5209a1ce2 CPU threads: 4; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: en-US Calc: threaded
Dear yanjingtao, 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
Also in Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded What I have notice that Trace Precedence is correctly finding the cells. See my screenshot. * Trace Precedence documentation: https://help.libreoffice.org/latest/lo/text/scalc/01/06030100.html
Created attachment 189913 [details] screenshot
In the first case, the Precedents are found just for B3, not for C3 (that is also selected), so, in this case could be a problem with Precedence being applied just to one cell that is selected. In the second example, it seems that the parameters for Precedence are found for the first cell (C14), but aplied to the second element in selection (B15).
Created attachment 197808 [details] video testing the bug
(In reply to BogdanB from comment #10) > In the first case, the Precedents are found just for B3, not for C3 (that is > also selected), so, in this case could be a problem with Precedence being > applied just to one cell that is selected. correction: "so, in this case could be a problem with Precedence being > applied just to one cell from the cells that are selected."