Created attachment 86050 [details]
a docx document showing the issue and its PDF renderings in both Word 2007 and LibreOffice 4.1
If you put a table as a sole content in a floating frame, the position of the frame seems to be ignored and the table gets laid out as if it is placed outside the frame. We have initially found the issue when we opend the document created using ABBYY OCR products.
I looked through some of the other bugs regarding frames, but could not find any bug exactly describing this issue. So I would like to report it as a new one.
Steps to reproduce:
I attach a docx document showing the issue. It is created using Word 2007 as follows:
1. Place a text box. Make it 'floating' by setting its horizontal and vertical position relative to the page.
2. Place a table into the text box.
3. Convert the text box into a frame.
4. Remove an empty paragraph after the table so it becomes a sole content inside the frame.
The table is wrongly positioned.
The table is positioned correctly as done with Microsoft Word.
Operating System: Windows 7
Version: 18.104.22.168 release
Thank you for your bug report,
I can reproduce this bug running libreoffice:
Build ID: Build ID: 410m0(Build:2)
OS: Ubuntu 13.04 64-bits
Created attachment 108790 [details]
screenshot 3.6.7 vs 4.0.4 vs 4.3.2
well, position is still wrongly set to the left, however the table size in 4.3.2 is now normal while it was larger in 4.1.1
both position and size of the table were like MS Word in LibO 3.6.7 and were abnormal in 4.0.4
hence that was a double regression of the 4.0.x branch with the size issue being fixed meanwhile but the position still persisting. see screenshot.
This is my first bibisect :-)
I hope I did not miss sth.
f6010f35e4b7789ef7bafcebc9b812b8a5492e26 is the first bad commit
Author: Bjoern Michaelsen <email@example.com>
Date: Wed Oct 16 11:07:50 2013 +0000
Author: Stephan Bergmann <firstname.lastname@example.org>
AuthorDate: Fri Mar 1 17:09:45 2013 +0100
Commit: Stephan Bergmann <email@example.com>
CommitDate: Fri Mar 1 17:18:29 2013 +0100
Related rhbz#915743: Abort UCB call from SvtMatchContext_Impl::Stop
...as otherwise the SvtMatchContext_Impl thread can continue to run for
arbitrarily long, and the other thread calling Stop() and join() will block.
However, especially the WebDAV UCP does not properly support aborting commands,
see 260afe56fd6b2f34de8290f3cdb7d1df5b88f8a8 " neon commands cannot be aborted",
so this is not yet enough to actually fix rhbz#915743 "thread deadlock/slow
join in insert->hyperlink in impress."
Although as indicated in the attached screenshot the behaviour has since changed somewhat, the original problem that the floating frame is lost is still present, and began at the below commit.
Adding Cc: to firstname.lastname@example.org. Could you possibly take a look at this? Thanks
Author: Cédric Bosdonnat <email@example.com>
Date: Mon Feb 18 17:34:06 2013 +0100
n#779642: ignore framePr inside table or the table import won't work
This issue is still present in
Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261
Locale: es-ES (es_ES)
on Windows 7 (64-bit)
This issue is still present in
Build ID: e6fade1ce133039d28369751b77ac8faff6e40cb
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-11-16_00:12:42
Locale: es-ES (es_ES)
on Windows 7
Migrating Whiteboard tags to Keywords: (bibisected)
** Please read this message in its entirety before responding **
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!
Created attachment 139492 [details]
docx document showing the issue
Created attachment 139493 [details]
docx document compared in MSO and Lo 6.1+
Repro in LO 6.1+. No frame.
*** Bug 112004 has been marked as a duplicate of this bug. ***
Repro LO 6.3+.