Bug 148034 - FILEOPEN: DOCX: multipage table is only displayed in one page
Summary: FILEOPEN: DOCX: multipage table is only displayed in one page
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected
Depends on:
Blocks: DOCX-Tables
  Show dependency treegraph
 
Reported: 2022-03-16 13:09 UTC by Xisco Faulí
Modified: 2022-06-24 14:12 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Comparison MSO 2010 and LibreOffice 7.4 master (533.84 KB, image/png)
2022-03-16 13:09 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2022-03-16 13:09:06 UTC
Created attachment 178915 [details]
Comparison MSO 2010 and LibreOffice 7.4 master

Steps to reproduce:
1. Open attachment 44014 [details] from bug 34911

-> The document has one page. it should have 2 instead. See comparison

Reproduced in

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: cfd82e7a2cc2b45b738eb0efa0827196d2de61a4
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

[Bug found by office-interoperability-tools]
Comment 1 Xisco Faulí 2022-03-16 13:09:54 UTC
Regression introduced by:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=3eb6d764b3023500f2299d36bf1860bc8e67db9f

author	Miklos Vajna <vmiklos@collabora.com>	2022-01-21 10:06:02 +0100
committer	Miklos Vajna <vmiklos@collabora.com>	2022-01-21 12:31:24 +0100
commit 3eb6d764b3023500f2299d36bf1860bc8e67db9f (patch)
tree 45880c2cd1f82a9abcae2b50068c56da55d1ee72
parent dde74d2ec45976a1de58296e79d9301f2cb1c001 (diff)
DOCX import: floating table with negative top margin has to be a fly frame

Bisected with: bibisect-linux64-7.4

Adding Cc: to Miklos Vajna
Comment 2 Miklos Vajna 2022-03-16 13:13:41 UTC
I'm afraid this is effectively a duplicate of bug 61594, i.e. Writer doesn't have multi-page floating tables and Word has. Or is there anything specific (bugfix category) that could be done here?
Comment 3 Xisco Faulí 2022-03-16 13:25:51 UTC
(In reply to Miklos Vajna from comment #2)
> I'm afraid this is effectively a duplicate of bug 61594, i.e. Writer doesn't
> have multi-page floating tables and Word has. Or is there anything specific
> (bugfix category) that could be done here?

so just to understand it, you commit changed the table in the document to be a floating table and now we are hitting bug 61594 ?
Comment 4 Miklos Vajna 2022-03-16 13:36:31 UTC
Exactly. And the table in the document has positioning information, so even if we import it as a non-floating table, then the content can be multi-page, but the positioning will be still incorrect.

I think it would be useful to keep this bugreport open, but I would argue this never really worked, so this is not a true regression.
Comment 5 Xisco Faulí 2022-03-16 14:18:18 UTC
(In reply to Miklos Vajna from comment #4)
> Exactly. And the table in the document has positioning information, so even
> if we import it as a non-floating table, then the content can be multi-page,
> but the positioning will be still incorrect.
> 
> I think it would be useful to keep this bugreport open, but I would argue
> this never really worked, so this is not a true regression.

fair enough
Comment 6 Justin L 2022-06-24 14:12:05 UTC
But there is no point in keeping it open as a separate bug report is there? Shouldn't we "close" it as a duplicate?