Bug 126153 - Tab key has to be pressed twice to enter text
Summary: Tab key has to be pressed twice to enter text
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-28 20:28 UTC by Chris Prior
Modified: 2019-12-28 14:22 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Prior 2019-06-28 20:28:12 UTC
Since upgrading to 6.2.4.2.0, calc has seemingly changed the behaviour of the tab key. Formerly, pressing tab would move to the next cell and permit immediate entry of text into that cell. Now, I have to press the tab key again to enter text. 
Once text has been entered, pressing tab moves the cursor forward to the next cell but does not allow text entry. Pressing any key after a single tab results in varying behaviour but is possibly seems to behave as if the ctrl key was held down. Pressing the tab key a second time does not move the cursor and then permits entry of text as normal.
I can find no settings within the menus that would seem to control this behaviour.

Linux kernel 4.19.52
gcc 8.3.0
kde plasma 5.57.0
Comment 1 V Stuart Foote 2019-06-28 23:01:54 UTC
Can not confirm on Windows builds of 6.2.4.2 or current master/6.4.0; a <Tab> into a Calc sheet's cell is immediately able to alter the cell content.

Please retest with a clean default user profile (done via the Help -> Restart in Safe Mode dialog.
Comment 2 Jan-Marek Glogowski 2019-06-28 23:41:19 UTC
Please provide the info from About -> Libre Office (text is selectable).

But since you explicitly mention kde plasma, I guess VCL is kde5 and it's quite probably a duplicate of bug 125548, which is fixed in 6.2.5.
Comment 3 QA Administrators 2019-12-26 03:25:20 UTC Comment hidden (obsolete)
Comment 4 Chris Prior 2019-12-27 17:47:19 UTC
Apologies - I downgraded to remove the problem and now have version 6.2.8.2 which does not display the behaviour noted. I can assume this has indeed be fixed.