This issue affect both Windows and Linux. Here is the two versions/environoments where the behaviour occur in: Windows 10 Version: 6.3.2.2 (x86) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; Locale: nb-NO (nb_NO); UI-Language: en-US Calc: CL Linux Lite 4.2 Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.2 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: nb-NO (en_US.UTF-8); Calc: group Look at the screen copies as it depict the issue. Steps to reproduce: * Open the attached file "libo-suggestion-error-example.ods" * Go to a cell similar contents to those in screen shot (e.g. cell M26) - last character is "a" or "b". * Edit cell, Put the cursor at end of text. * Press Back on keyboard to remove last character * then enter "a" or "b" Expected behavior: Behaves like any normal text edior, hitting Enter key makes the cursor go out of cell-edit mode, and the inserted character stay put. Observed behavior: After enter the last character in cell, Calc suggest a formula to insert. Since user expect Calc to insert only "a", user may not be aware until after Enter is presset and must then go back to re-edit the contents of the cell. Consistency: The observed behaviour may or may not affect editng on any cell. If the behaviour seems not being present, then just move down to next cell until the beavior occur. I'm not able to predict which cells will be affected. It also may occur on different cells on different computers. Workaround: There is no actual workaround on this, but if user is aware that the behavior can occur at any time, then when the press any arrow key on keyboard to cancel the function suggestion and get back to normal text editing mode, then press Enter to get out of cell edit mode.
Created attachment 156553 [details] Screen shot Windows 10
Created attachment 156554 [details] Screen shot Linux Linux Lite 4.2 LibO Version: 6.0.7.3 / Build ID: 1:6.0.7-0ubuntu0.18.04.2
Created attachment 156555 [details] Spread sheet where the behavior is observed Coloumn M is affected by this - see description in bug repport
I can't reproduce it in Version: 7.0.0.0.alpha0+ Build ID: 28d844a589e52abfe62dc66b888e78665221ba28 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: x11; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded nor in Versión: 6.4.0.3 (x86) Id. de compilación: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8 Subprocs. CPU: 2; SO: Windows 6.1 Service Pack 1 Build 7601; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded
but I do if wildcards are enabled ( Tools - Options - Calc - Calculate - Formula Wildcards )
(In reply to Xisco Faulí from comment #5) > but I do if wildcards are enabled ( Tools - Options - Calc - Calculate - > Formula Wildcards ) @Eike, I think it was you who implemented it. Could you please comment on whether it's the expected behaviour ?
That's just the normal function names tooltip, and no, it wasn't me who implemented it, but I reviewed the code back then. The awkward thing here is that a cell content starting with a + plus character (and also - minus character fwiw) is regarded as a formula entry (for those data typists who are working on the numeric keypad). We maybe could disable the tooltips if the entry does not start with a = equal character, or even better have an option whether +|- should start a formula (which more often gets in the way than not). (In reply to Xisco Faulí from comment #5) > but I do if wildcards are enabled ( Tools - Options - Calc - Calculate - > Formula Wildcards ) Completely unrelated. The tooltip is displayed with or without, unless disabled with Tools -> AutoInput.
(In reply to Eike Rathke from comment #7) > That's just the normal function names tooltip, and no, it wasn't me who > implemented it, but I reviewed the code back then. The awkward thing here is > that a cell content starting with a + plus character (and also - minus > character fwiw) is regarded as a formula entry (for those data typists who > are working on the numeric keypad). We maybe could disable the tooltips if > the entry does not start with a = equal character, or even better have an > option whether +|- should start a formula (which more often gets in the way > than not). UX evaluation needed for the option implementation
(In reply to Eike Rathke from comment #7) > We maybe could disable the tooltips if the entry does not start with > a = equal character, or even better have an option whether +|- should > start a formula (which more often gets in the way than not). The function could be labeled "[ ] Direct numpad mode" (or something else) with a tooltip "Enable this option to use +/- from the numpad to start a function without the need to use = at the beginning" (terrible English; needs more advanced speaker). It should be off by default as users who get annoyed by the tooltip won't find the right checkbox easily. Nice easyhack with medium difficulty.
Dear Grobe, 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
Can still reproduce with that same file. Version: 7.2.7.2 Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: nb-NO (en_US.UTF-8); UI: en-US Calc: threaded This is the particular steps I did to reproduce: * Open document in Libre Office * Put cursor in cell M26 * Hit F2 to edit. * Hit back * Hit "a" + Enter * Hit Up and F2 (to edit same dell again) * Hit back * Hit "b" + Enter * Repeat for M27 * Hit Enter twice to go to M30 * Hit F2 and Back * Hit "a" Now, Calc would suggest insertion of the formula similar as shown in screenshots added back in 2019.