Bug 128027 - Using tab in a spreadsheet on iOS 13 leads to unexpected behavior
Summary: Using tab in a spreadsheet on iOS 13 leads to unexpected behavior
Status: RESOLVED DUPLICATE of bug 128506
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: iOS Editor (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other iOS
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-08 14:42 UTC by Nicolas Christener
Modified: 2019-11-08 10:13 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 Nicolas Christener 2019-10-08 14:42:31 UTC
Description:
In iOS 13 some keys on a hardware keyboard that previously didn't work now do something. It seems, that the tab key (tabulator) doesn't do the right thing in a spreadsheet.

While the tab key moves the visual cell selection the focus seems to jump to the horizontal scrollbar. See "Steps to Reproduce" below for more information.

Steps to Reproduce:
1. Open a spreadsheet on iOS 13
2. Enter "hello" into a cell
3. Press the tab key on the hardware keyboard
4. Enter "world"

Actual Results:
The letters typed after pressing the tab key won't show up.

Expected Results:
The letters typed after pressing the tap key should show up in the cell next to the one which shows "hello".


Reproducible: Always


User Profile Reset: No



Additional Info:
It's also not possible to move the cell selection with the arrow keys but when using the left/right arrow keys one can see that the horizontal scrollbar moves. 

To me it seems that the tab key doesn't move the focus to the next cell but to an other widget.
Comment 1 Xisco Faulí 2019-10-14 15:46:23 UTC
Moving to NEW as agreed in the ESC meeting
Comment 2 How can I remove my account? 2019-11-08 10:13:55 UTC
Seems to be fixed by the same change as bug #128506. Which makes sense, as the keyboard handling on mobile devices is handled by the same JS code. Marking as duplicate.

*** This bug has been marked as a duplicate of bug 128506 ***