Bug 155378 - Can't leave cell in Calc using Right arrow when autocomplete is suggesting
Summary: Can't leave cell in Calc using Right arrow when autocomplete is suggesting
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.3.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: implementationError
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2023-05-17 21:02 UTC by Tomas
Modified: 2025-05-20 03:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screen recording mp4 using H265 (222.13 KB, video/mp4)
2023-05-19 17:34 UTC, Tomas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas 2023-05-17 21:02:56 UTC
Description:
Having cell A1 text "fo" and A2 text "f" and entering "f" into A3 I can't leave cell with pressing Right arrow once but I have to press it twice. It seems to be connected with autocomplete from "fo".

Steps to Reproduce:
1. Create new Calc spreadsheet.
2. Enter fo into A1 and press Enter
3. Enter f into A2 and press Enter
4. Enter f into A3 and press RIGHT arrow to leave cell and focus B3



Actual Results:
Nothing happens, cell remains in editing state. Only after pressing RIGHT arrow again cell A3 is left and B3 is focused.

Expected Results:
After first press of RIGHT arrow it should leave A3 and focus B3.


Reproducible: Always


User Profile Reset: No

Additional Info:
This worked for years in versions before.
Comment 1 Stéphane Guillou (stragu) 2023-05-19 09:49:44 UTC
I can't reproduce in:

Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 1349f140fcc49e5da78482ca3db09663ccdae0a9
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Nor in:

Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Which version and OS do you use? Please paste here the info copied from the About dialog.
Comment 2 Tomas 2023-05-19 16:36:36 UTC
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: en-US (sk_SK); UI: en-US
Calc: CL threaded

also in

Version: 7.3.7.2 / LibreOffice Community
Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f
CPU threads: 4; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-IE (en_SK.UTF-8); UI: en-US
Calc: threaded
Comment 3 Tomas 2023-05-19 17:34:02 UTC
Created attachment 187405 [details]
screen recording mp4 using H265
Comment 4 Tomas 2023-05-19 17:42:20 UTC
There is one small mistake in Steps to reproduce. First you have to enter f and then fo in order to use Enter to close the cell.
Comment 5 ady 2023-05-20 02:24:44 UTC
Repro since 7.3, and the reason is clear:
https://wiki.documentfoundation.org/ReleaseNotes/7.3#Calc
"
Bash like autocompletion for Calc autoinput was implemented. tdf#145198 (Dennis Francis, Collabora)
"
IMNSHO that changed autoinput was (quasi) forced onto us (users) in spite of many complaints and opinions against it – and not all of them were solved.
FWIW, [TAB] still reacts on first press, whereas arrows have been borrowed/stolen for bash autoinput.
Comment 6 Stéphane Guillou (stragu) 2023-05-20 07:03:09 UTC
Thanks Ady, confirmed that it started at commit 4cfa840ecaa5a094a32a60a60b295858980109df (or commit fadef6d84eaca0b8e505f2e315447be92802d757 in linux-64-7.3 bibisect repo).

With Tomas' steps, it clearly feels like a bug in that there's no hint that it is related to autocomplete: it doesn't "accept" an autocompletion string.

Dennis, can you please have a look?
Comment 7 QA Administrators 2025-05-20 03:10:55 UTC
Dear Tomas,

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