Bug 109173 - Freeze First Row works only sometimes
Summary: Freeze First Row works only sometimes
Status: RESOLVED DUPLICATE of bug 100666
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2017-07-17 18:10 UTC by pavelz
Modified: 2023-01-20 14:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description pavelz 2017-07-17 18:10:18 UTC
Freeze First Row does nothing when the row "1" is not visible on the current screen, but the command is shown as active/available in the menu and toolbar.

The behaviour is quite misleading, but I am not sure what is the proper expected behaviour. M$ Excel freezes the topmost row of the current screen.

Steps to Reproduce:
1. Open new spreadsheet
2. Scroll down so the row "1" is not visible
3. Select "Freeze First Row" either from toolbar button or from the menu (View - Freeze Cells - Freeze First Row)

Actual Results:  
Nothing happens.

Expected Results:
Either the topmost row should be frozen, or the row "1" should be frozen and the current screen adjusted, or the command to Freeze First Row should be inactive/unavailable in such a situation.

Reproducible: Always

User Profile Reset: 

Additional Info:
It is similar for Freeze First Column, just scroll to the right (Shift+Scroll) so the column "A" is not visible on the current screen.

Reproducible also in current master.

Build ID: cf0a9b9c7a988b74102bcdd38710fb9e80521081
CPU threads: 2; OS: Linux 4.11; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-07-17_13:35:14
Locale: cs-CZ (cs_CZ.UTF-8); Calc: group

User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Comment 1 Gabor Kelemen (allotropia) 2017-07-18 07:29:07 UTC

*** This bug has been marked as a duplicate of bug 100666 ***
Comment 2 Aron Budea 2022-07-20 02:46:46 UTC

*** This bug has been marked as a duplicate of bug 112641 ***
Comment 3 Justin L 2023-01-20 14:59:14 UTC

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