Bug 153340 - Table - Edit - Insert Row between existing rows often does not work
Summary: Table - Edit - Insert Row between existing rows often does not work
Status: RESOLVED DUPLICATE of bug 71224
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.5.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-03 06:07 UTC by Peter
Modified: 2023-02-03 07:58 UTC (History)
0 users

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 Peter 2023-02-03 06:07:21 UTC
Description:
When I need to insert a row between existing rows in a table design, the Insert Row command often doesn't work. Instead, it moves the cursor to the end of the field list and attempts to insert the row there. This issue existed in V7.4 also. I like to keep my table designs neat and tidy by listing indexed fields used in table relationships together at the top of the table layout.

Steps to Reproduce:
1.Edit a preexisting table having at least 2 rows
2.Right click in the column to the left of the field name
3.Choose Insert Rows



Actual Results:
In my case the cursor shifts to the row after the second row to insert the row at that point.

Expected Results:
A new empty row should appear at the point I chose, and all subsequent rows should shift downwards.


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: OfficeDatabaseDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes

Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 16; OS: Windows 11.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: CL threaded
Comment 1 Stéphane Guillou (stragu) 2023-02-03 07:58:23 UTC
Thank you for your report, Peter. This has been reported before in bug 71224.

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