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]
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
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?
(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 ?
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.
(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
But there is no point in keeping it open as a separate bug report is there? Shouldn't we "close" it as a duplicate?
This is now 2 pages in 7.6 since https://git.libreoffice.org/core/commit/ce3308a926f036b87515b8cd97d2b197063dc77a tdf#61594 sw floattable: import floating tables as split flys by default *** This bug has been marked as a duplicate of bug 61594 ***