Bug 137191 - Vertically wrong aligned text within cell after opening file
Summary: Vertically wrong aligned text within cell after opening file
Status: RESOLVED DUPLICATE of bug 133946
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-01 17:21 UTC by Ettore Atalan
Modified: 2020-10-02 06:57 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test Document (10.94 KB, application/vnd.oasis.opendocument.text)
2020-10-01 17:21 UTC, Ettore Atalan
Details
Vertically wrong aligned text within a cell after opening Test Document (63.05 KB, image/png)
2020-10-01 17:23 UTC, Ettore Atalan
Details
Vertically correct aligned text after clicking on cell (64.22 KB, image/png)
2020-10-01 17:24 UTC, Ettore Atalan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ettore Atalan 2020-10-01 17:21:27 UTC
Created attachment 166005 [details]
Test Document

A text set as vertically centered within a cell of a table is displayed incorrectly after opening the attached Test Document.

If you click in the relevant cell, the text will automatically align itself correctly.


Tested in LibreOffice 6.4.6 and 7.0 (on Windows and on Ubuntu Linux).
Comment 1 Ettore Atalan 2020-10-01 17:23:29 UTC
Created attachment 166006 [details]
Vertically wrong aligned text within a cell after opening Test Document
Comment 2 Ettore Atalan 2020-10-01 17:24:53 UTC
Created attachment 166007 [details]
Vertically correct aligned text after clicking on cell
Comment 3 Dieter 2020-10-02 06:57:29 UTC
I confirm it with

Version: 7.1.0.0.alpha0+ (x64)
Build ID: 8c18cd6823ddf4ef5ba67801a84cee26c9b5a9a6
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded

But it is a duplicate of bug 133946

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