Bug 91876 - EDITING: Ctrl+D followed by F2 acts as if Ctrl+D hadn't been pressed
Summary: EDITING: Ctrl+D followed by F2 acts as if Ctrl+D hadn't been pressed
Status: RESOLVED DUPLICATE of bug 54197
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.3.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-05 15:27 UTC by Andy Goth
Modified: 2015-06-08 18:52 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 Andy Goth 2015-06-05 15:27:47 UTC
Pressing F2 immediately after pressing Ctrl+D opens in-cell editing but shows the cell contents prior to Ctrl+D having been pressed.

Scenario 1:
1. Open new spreadsheet.  Cursor is positioned on A1.
2. Type "xxx" and press Enter.  Cell A1 shows "xxx", cursor moves to A2.
3. Press Ctrl+D.  Cell A2 shows "xxx".
4. Press F2.  Entry is opened in A2 but shows no text.
5. Press Escape.  Entry is canceled, and cell A2 shows "xxx".
6. Press F2.  Entry is opened in A2 but shows no text.
7. Press Escape.  Entry is canceled, and cell A2 shows "xxx".
8. Switch to another window, e.g. with Alt+Tab, then switch back.
9. Press F2.  Entry is opened in A2 and shows "xxx".

Scenario 2:
1. Open new spreadsheet.  Cursor is positioned on A1.
2. Press down.  Cursor moves to A2.
3. Type "xxx" and press Up.  Cell A2 shows "xxx", cursor moves to A1.
4. Type "yyy" and press Enter.  Cell A1 shows "yyy", cursor moves to A2.
5. Press Ctrl+D.  Cell A2 shows "yyy".
6. Press F2.  Entry is opened in A2 but shows "xxx".

Other actions, for instance cursor movement between Ctrl+D and F2, also avoid the problem.  So far I only see an issue when F2 immediately follows Ctrl+D, though using Escape and F2 again doesn't help.
Comment 1 raal 2015-06-08 12:11:40 UTC
Hello Andy,

Thank you for reporting the bug. Can you see if bug 54197 is similar to your problem so that I can mark your report as a duplicate of it? (Later bugs are generally marked as duplicates of earlier bugs).
Comment 2 Andy Goth 2015-06-08 16:29:42 UTC
Yes, this is a duplicate.  Thank you for finding it.

I'm curious why there are six or seven duplicates already, yet none of them came to my attention when I searched for duplicates prior to filing this bug report.  Whatever, that's behind us now.
Comment 3 raal 2015-06-08 18:52:29 UTC

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