The first and the second table is slipping into one another.
Steps to Reproduce:
1. Opening the attachment in Microsoft Word.
2. Opening the attachment in LibreOffice Writer.
The first and the second table is not slipping into one another.
User Profile Reset: No
Created attachment 143586 [details]
The original file.
Created attachment 143587 [details]
The tables in Word (good result).
Created attachment 143588 [details]
The tables in Writer (bad result).
It seems, one of the tables is there in a frame unnecessarily. (Unfortunately, it's very easy to do that unintentionally in MS Word with the table handles.)
Reproduced back to
Version 184.108.40.206.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
but not in
Bibisected to the following range using repo bibisect-43all.
Almost certainly caused by making the table floating from
Miklos Vajna 2012-08-21 17:48:13 +0200
n#775899 initial docx import of w:vertAnchor inside w:tblpPr
But the wrapping code obviously isn't working in this case, so more like it exposed another problem than caused a regression. The first table IS supposed to be a floating table as mentioned in comment 4.
Dear Pénzes Dávid,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Fixed for LO 7.0 by commit fd7749fddc5a767461dfced55369af48e5a6d561
Author: Miklos Vajna Fri Feb 14 16:29:44 2020 +0100
sw: fix handling of table vs fly overlaps in the AddVerticalFlyOffsets case
Thanks for updating this bug! I'm not great at searching for duplicates in bugzilla.
Indeed. Verified in
Build ID: c8d764b3f27c2bb0712745891b70630e94436317
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
*** Bug 78755 has been marked as a duplicate of this bug. ***
*** Bug 115188 has been marked as a duplicate of this bug. ***