Bug 166159 - Bug: Calc- When editing comment in cell adjacent to frozen row
Summary: Bug: Calc- When editing comment in cell adjacent to frozen row
Status: RESOLVED DUPLICATE of bug 126847
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
25.2.2.2 release
Hardware: x86 (IA32) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-13 00:35 UTC by Jay York
Modified: 2025-04-13 01:21 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 Jay York 2025-04-13 00:35:23 UTC
Description:
EDITING...
Calc; Libre Office v 25.2.2; Intel 64-Bit:
When editing (and possibly when creating) a Comment field adjacent to a frozen row -- in my case, immediately above a frozen row-- with text that is deeper than the default, the Comment field will not expand or scroll down to reveal the text you're typing.  Once finalized, the Comment field displays correctly.

Workaround: Unfreeze the row. Edit the deeper text in the Comment field. Re-freeze the row.



Steps to Reproduce:
1. Leaving a few rows above, freeze a row
2. A a Comment in a cell immediately above the frozen row.  (may exhibit same problem below the frozen row; didn't try that)
3. Type text in the Comment field, entering enough that it disappears out of sight in the Comment field
4. Finalize the Comment

Actual Results:
Text I typed was in the Comment field but I couldn't see it, correct any typos, or format it until I finalized the Comment field.

Expected Results:
Comment field should scroll or expand downward as needed... in this case below the frozen row.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows 11
OS is 64bit: yes-- well, the OS is.  Did I install the wrong version of Office?
Comment 1 m_a_riosv 2025-04-13 01:21:42 UTC

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