Bug 170265 - enhancement: adapt freezed rows when rows above are inserted/deleted
Summary: enhancement: adapt freezed rows when rows above are inserted/deleted
Status: RESOLVED DUPLICATE of bug 99570
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
26.2.0.0 alpha0+ master
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks:
 
Reported: 2026-01-08 10:01 UTC by Michael Otto
Modified: 2026-01-12 06:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
table with more than 1 row above the data and rows freezed (28.13 KB, application/vnd.oasis.opendocument.spreadsheet)
2026-01-08 10:01 UTC, Michael Otto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Otto 2026-01-08 10:01:50 UTC
Created attachment 204971 [details]
table with more than 1 row above the data and rows freezed

PRECONDITION:
in a table with more than 1 header row above the data
set View > Freeze Rows and Columns (not in row 2 but e.g. row 5)
see e.g. attached trainstat-multiheader.ods

PROBLEM DESCRIPTION:
insert another row in the header
   set cursor to a row above the freezed row
   Sheet > Insert Rows > Rows above

the freezed rows stay at the row number as initially selected 
==> the table does no more scroll at desired row

EXPECTED BEHAVIOR:
the freezed row shall be shifted by the inserted rows (same for deleted rows)


Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 480ef73deef62c458e5735cd496a1d74ef408ed8
CPU threads: 2; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded
Comment 1 Werner Tietz 2026-01-08 17:55:03 UTC
(In reply to Michael Otto from comment #0)

> 
> EXPECTED BEHAVIOR:
> the freezed row shall be shifted by the inserted rows (same for deleted rows)

+1
Comment 2 Heiko Tietze 2026-01-12 06:10:48 UTC
You probably also want to shift if rows are deleted. While there might be cases when the opposite is expected I can imagine this use case is more common.

Same report in bug 106440 being itself a duplicate of bug 99570.

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