Created attachment 132240 [details] Position problem with image and table in same line Open attached file. In LibreOffice the table is left aligned and the image is in front of the table. In Word the image is first in the line and the table is after the image, with no overlapping.
Confirmed in - Version: 5.4.0.0.alpha0+ Build ID: 6152bf9ee9b2e348dee854921a5a5db1cfc72995 CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e - Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) - LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Created attachment 132241 [details] How it looks in MSO 2010
** 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! Warm Regards, QA Team MassPing-UntouchedBug
The problem still exists in Version: 6.1.0.0.alpha0+ (x64) Build ID: fe1c13d4ba288e45acdba5bc01b0ef81da08f125 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: CL
still repro in Версия: 6.3.0.0.alpha0+ ID сборки: 51af3179cf972809d6495c7d58033e069f647bbf Потоков ЦП: 4; ОС:Linux 4.18; Отрисовка ИП: по умолчанию; VCL: kde5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-02-01_00:15:00 Локаль: ru-RU (ru_RU.UTF-8); UI-Language: ru-RU Calc: threaded
I don't think this is a DOC issue. Try to create such a thing in ODT format. I couldn't do it. I don't think LO has the ability to wrap tables.
*** Bug 119914 has been marked as a duplicate of this bug. ***
(In reply to Justin L from comment #6) > I don't think this is a DOC issue. Try to create such a thing in ODT format. > I couldn't do it. I don't think LO has the ability to wrap tables. Bug 117132 is an enhancement request on this feature, let's set it as a prerequisite.
Confirmed Version: 7.0.4.2 Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 12; OS: Linux 5.8; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL
Let's reset status to NEW, even if this depends on a missing feature in Writer, there should be a DOC format handling aspect once the feature is developed (or ideally, the DOC/DOCX parts would be developed together with the feature, since it's mainly for interoperability at this point).
*** This bug has been marked as a duplicate of bug 76022 ***