Bug 108647

Summary: Multi lines comments are not well displayed while editing
Product: LibreOffice Reporter: Benjamin <benjamin.poulain>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: raal, xiscofauli
Priority: medium Keywords: bibisectRequest, regression
Version: 4.1 all versions   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 101216    
Attachments: 3 screens with the bug
Column "J" have a multi line comment non editable

Description Benjamin 2017-06-20 12:44:58 UTC
Created attachment 134159 [details]
3 screens with the bug

Condition : 
- Comment on first line
- Use Display -> Fixe cells -> Fixe first line

When creating or editing a comment on a cell, only the first line is displayed.
See screenshots.
Comment 1 Timur 2017-06-22 16:10:30 UTC
Please give exact minimal steps to reproduce from empty document. And attach sample table. 
Please use English menus, not clear what id Display and what is Fixe first line (View-Freeze First Rolw?).
Comment 2 Benjamin 2017-06-26 07:49:36 UTC
Created attachment 134285 [details]
Column "J" have a multi line comment non editable

Here comes an example.
If you try to edit the comment on column J, only the first line of the comment is viewable.
If you disable the option "View --> fixe first line", all the comment is editable.
Comment 3 Xisco FaulĂ­ 2017-06-26 15:35:34 UTC
Confirmed in

- Version: 6.0.0.0.alpha0+
Build ID: 08f6f9dded1b142b858c455da03319abac691655
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

- Version: 5.0.0.0.alpha1+
Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86
Locale: ca-ES (ca_ES.UTF-8)

- Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e

- Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)

but not in

- LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 4 raal 2017-06-26 16:48:19 UTC

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