Created attachment 92268 [details] .xlsx doc with the bug I have a .xls-document with column k containing strings of a couple of hundreds characters. Also I pulled down the formulabox to show more than one line, thus showing the entire field. The bug is that navigating with arrow-up or arrow-down does not change the formulabox if the first line of the box is the same. Also happens if I save the document as .ods If you go from one cell to the other, and the first line of the box is the same as the previous cell, then the contents of the formula box does not change. No harm, except when there are differences in character beyond that. In that case you see the string of the previous cell and not the string of the other cell. If you do the same but navigate by clicking instead of the arrows, then the contents of the formula box does change, as expected. Also if you make the window wide enough, making the formula box wide enough and thus change the first line upon navigating, then the contents of the formula box does change, as expected.
Comment on attachment 92268 [details] .xlsx doc with the bug fixing mime type
I do not understand: the formulabox shows the first line of the formula. Where is the problem? If I pull down the formulabox to see more than one line, I see what is shown on the cell when I navigate with arrow up and down keys. Please, could you attach a screenshot showing the problem? Best regards. JBF
Created attachment 92445 [details] Starting position From this starting position, press Arrow-up, taking you to K4. Formulabox does not change, although the cell value of K4 is different to K5 (...utm_term=bedanktemail... instead of ...utm_term=bedanktpagina...) Press Arrow-down 4 times, nothing changes, you are in K9 now. Press Arrow down once more going to K10, formulabox changes. (...utm_medium=auto... changes to ...utm_medium=recht...) Clicking a cell almost always changes the formulabox correctly. Except if you click after having pressed Arrow-up(or down) without the formulabox changing. For instance: go to K6, press arrow-up. Now click K4, K5, K7, K8 or K9. Formulabox stays the same. Now click anywhere else, Formulabox changes nicely. Now click K4, K5, K7, K8 or K9 again. Formulabox changes nicely. Kind of weird.
I do not reproduce with generic Linux version 4.1.4.2 and with my own build of 4.2.1.0.0+ on Ubuntu 13.10 x86-64. It would be very useful if you could install the current generic Linux version and check if you still encounter the same behavior. Best regards. JBF
I confirm the bug on LibO 4.2.0.3 rc on Win7. The key point to reproduce the bug is to have the formula box bit wide enough so that the content is wrapped to 3 lines at minimum, in the formula box expanded by the "Expand Formula Bar" arrow.
(In reply to comment #5) > I confirm the bug on LibO 4.2.0.3 rc on Win7. > > The key point to reproduce the bug is to have the formula box bit wide > enough so that the content is wrapped to 3 lines at minimum, in the formula > box expanded by the "Expand Formula Bar" arrow. Indeed, you are right. Now I can reproduce the problem with LO 4.2.1.0.0+ on Ubuntu 13.10. Best regards. JBF
** 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 (4.4.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-05-02
(In reply to Dominique Boutry from comment #5) > I confirm the bug on LibO 4.2.0.3 rc on Win7. > > The key point to reproduce the bug is to have the formula box bit wide > enough so that the content is wrapped to 3 lines at minimum, in the formula > box expanded by the "Expand Formula Bar" arrow. Repro. 2 lines is ok, but when I made the LibO window narrower so they go to 3 lines, they stopped updating (except when going over 8 & 9). Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58 Locale: fi-FI (fi_FI)
** 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
Still reproducible in LO 5.2.3.0+ and current master, both built at home under Ubuntu 16.04 x86-64. Best regards. JBF
** 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.4.1 or 5.3.6 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-20170929
Still reproducible with current master built at home under Ubuntu 16.04. Best regards. JBF
** 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
Not reproducible anymore with LO 6.2.0.1.0+ under Ubuntu 18.04. Closing as WorkForMe. Please, feel free to reopen if you disagree. Best regards. JBF