Bug 162637 - Vertical merged column not rendered
Summary: Vertical merged column not rendered
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-26 07:58 UTC by Yvan Lussaud
Modified: 2024-08-26 14:51 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
the document with the rendering issue (12.16 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2024-08-26 07:58 UTC, Yvan Lussaud
Details
The actual rendering (11.50 KB, image/png)
2024-08-26 07:58 UTC, Yvan Lussaud
Details
The expected rendering (15.99 KB, image/png)
2024-08-26 07:59 UTC, Yvan Lussaud
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yvan Lussaud 2024-08-26 07:58:21 UTC
Created attachment 196021 [details]
the document with the rendering issue

The first vertically merged cells in the attached document is not rendered as the following ones, only one cell is rendered at the top. The content of the cells and rows for other vertically merged cells seems the same and are rendered as expected.
Comment 1 Yvan Lussaud 2024-08-26 07:58:54 UTC
Created attachment 196022 [details]
The actual rendering
Comment 2 Yvan Lussaud 2024-08-26 07:59:37 UTC
Created attachment 196023 [details]
The expected rendering
Comment 3 m_a_riosv 2024-08-26 14:15:31 UTC
Opening the file with
Microsoft® Word para Microsoft 365 MSO (versión 2407 compilación 16.0.17830.20056) de 64 bits 
and resaving it with Word, allows opening fine with LibreOffice.
Version: 24.8.0.3 (X86_64) / LibreOffice Community
Build ID: 0bdf1299c94fe897b119f97f3c613e9dca6be583
CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
Comment 4 Yvan Lussaud 2024-08-26 14:51:49 UTC
OK I'll try to do the same and see what differences are in the saved document. So this bug might be invalid.