Bug 101266 - Adding or editing comments screws up keyboard editing and navigation
Summary: Adding or editing comments screws up keyboard editing and navigation
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.2.0.1 rc
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-03 07:03 UTC by Dan Dascalescu
Modified: 2016-08-14 02:21 UTC (History)
3 users (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 Dan Dascalescu 2016-08-03 07:03:03 UTC
1. Open the XSLX from bug 100709
2. Add a comment to a cell, e.g. "foo" to C9424 and press Escape to finish inserting the comment
3. Edit another cell by pressing F2. Notice the cursor is at the end of the cell text.

From now on, text input and navigation are screwed up.

4. Now press Home. Notice how the cursor moves to column A, instead of moving to the start of the cell.
5. Instead of Home above, press left arrow. Notice how the cursor moves to the previous cell in the row, instead of to the previous character in the cell.
6. Click on an empty cell and try to type "foo". Only "f" will be entered.
7. Press Esc. The mouse cursor takes an "insertion" icon, and if you move the mouse, it looks like crosshairs with an "I" in the lower right.
Comment 1 Buovjaga 2016-08-07 13:22:06 UTC
I don't see the problem.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.2.0.4
Build ID: 5.2.0-1
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Comment 2 Joel Madero 2016-08-07 16:14:10 UTC
Version: 5.3.0.0.alpha0+
Build ID: fc305bb6d656736bedc2f89789e18d8c9a3bbf2c
CPU Threads: 2; OS Version: Linux 3.16; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group

Cannot confirm. Try with a fresh profile. https://wiki.documentfoundation.org/UserProfile
Comment 3 Aron Budea 2016-08-14 02:21:14 UTC
Reproduced with v5.2.0.1 / Windows 7.
Not reproduced with v5.2.0.4 / Windows 7.

Seems fixed, closing as WORKSFORME, return status to UNCONFIRMED if the issue still occurs in a current version.