Bug 59568 - FORMATTING: Automatic linebreak does not adapt row height
Summary: FORMATTING: Automatic linebreak does not adapt row height
Status: RESOLVED DUPLICATE of bug 59193
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.0.0.1 rc
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-01-18 17:59 UTC by Helmut Leininger
Modified: 2013-01-23 10:47 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
spreadsheet with wrong formatting (637.72 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-01-18 17:59 UTC, Helmut Leininger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Leininger 2013-01-18 17:59:02 UTC
Created attachment 73250 [details]
spreadsheet with wrong formatting

Problem description: 

Steps to reproduce:
1. insert new row
2. seit automatic linebreak for a cell
3. enter data

Current behavior:
only last line is shown, row height is not adapted, remains too small

Expected behavior:
adapt row height
              

look at the attached spreadsheet, sheet "Grinzing", rows 496, 498, 555 which have been inserted using LO 4.0.0.1 RC

Operating System: Windows 8
Version: 4.0.0.1 rc
Last worked in: 3.6.4.3 release
Comment 1 Michel Rudelle 2013-01-19 10:54:31 UTC
I confirm
(I understand that "automatic linebreak" means "Wrap text automatically" - is that correct ?)
I reproduce with the attached spreadsheet and my own documents

This happens only with spreadsheets created with previous version of LibreOffice
If you copy the sheet in a new document with LibO 4.0.0 rc1, it works correctly

Version 4.0.0.1 (Build ID: 527dba6f6e0cfbbc71bd6e7b88a52699bb48799) - Vista
Comment 2 Helmut Leininger 2013-01-19 11:03:38 UTC
@Michel Rudelle
you are right. I am using the German version where it is "Automatischer Zeilenumbruch"
Comment 3 Markus Mohrhard 2013-01-23 10:47:06 UTC

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