Bug 69804 - VIEWING: The attached file is not rendering correctly
Summary: VIEWING: The attached file is not rendering correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-09-25 10:34 UTC by ringe
Modified: 2013-09-30 17:44 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
A Microsoft Word document with a table (17.50 KB, application/msword)
2013-09-25 10:34 UTC, ringe 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ringe 2013-09-25 10:34:13 UTC 
Created attachment 86551 [details]
A Microsoft Word document with a table

Problem description: The attached file is not rendering correctly, the cells are compressed height-wise to make the text unreadable.

However, if I print the document it will render correctly after.

Steps to reproduce:
1. Open the attached document
2. See the unreadable text
3. Ctrl+P (print the document)
4. The document renders how it should

Current behavior:
The text in the document's table is unreadable after opening.

Expected behavior:
The text should render correctly and be readable.
Operating System: Windows (other)
Version: 4.0.4.2 release
Last worked in: 4.0.2.2 release
Comment 1 Thomas van der Meulen [retired] 2013-09-25 15:17:13 UTC 
Thank you for your bug report, I CAN'T reproduce this bug running Version 4.0.5.2 (Build ID: 5464147a081647a250913f19c0715bca595af2f) on Mac osx 10.8.4.
Comment 2 Thomas van der Meulen [retired] 2013-09-27 15:17:35 UTC 
Ringe, could you please attach a screenshot of what you see and how it should be renderd corretly. 

Thank you in advance, 
Thomas
Comment 3 ringe 2013-09-30 17:44:16 UTC 
I am unable to reproduce this bug now. I don't know what caused it and why it stopped being a problem. Possibly something to do with a Windows user session.