Description: FILEOPEN DOCX: Image positioned wrongly Steps to Reproduce: 1. Open the attached file The image Ministerie van Economische zaken en klimaat on page 1 should be in the right corner Actual Results: Somewhere in the middle of the page Expected Results: Image left corner Reproducible: Always User Profile Reset: No Additional Info: Found in 7.1 and in Version: 6.2.0.0.alpha0+ Build ID: 9d754a59154c40235c240bb0e7f47a2006fa85bd CPU threads: 4; OS: Windows 6.3; UI render: GL; Locale: nl-NL (nl_NL); Calc: CL
Created attachment 166757 [details] Export PDF word 2003 with conversion pack
Created attachment 166758 [details] Example file
Also in Versie: 5.1.6.2 Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909 CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: GL; Locale: nl-NL (nl_NL); Calc: CL looking even worse in 4.4.7.2
Also in Versie: 5.0.6.3 (x64) Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa Locale: nl-NL (nl_NL)
Created attachment 166768 [details] Comparison MSO 2010 and LibreOffice 7.1 master
Reproduced in Version: 7.1.0.0.alpha1+ Build ID: 0f0a5b63b19196f9463149a0a1991704c940efe2 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Created attachment 166775 [details] Example compared in different editors Here is the example compared in different editors. LO is unfortunately worse. This is not image, but frame with Wrap Around. So likely another duplicate.
Created attachment 167930 [details] Minimized example file Looks like it's enough to have a non-floating normal table in a frame to reproduce this problem, no image and no placement in header-footer is necessary.
Created attachment 167931 [details] The minimized example file in Word and Writer 7.2master Version: 7.2.0.0.alpha0+ (x64) Build ID: 561e5559bb68242c7f785f0ca3bee3eb12b58963 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: CL
(In reply to NISZ LibreOffice Team from comment #9) > Created attachment 167931 [details] > The minimized example file in Word and Writer 7.2master > > Version: 7.2.0.0.alpha0+ (x64) > Build ID: 561e5559bb68242c7f785f0ca3bee3eb12b58963 > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win > Locale: en-US (hu_HU); UI: en-US > Calc: CL FWIW.. the content below the frame is 'NEW' since 6.4. Previously both where overlapping. Adding bibisectrequest more to get grasp of code area.. but well NISZ surely better in assessing of this is worthwhile
(In reply to Telesto from comment #10) > FWIW.. the content below the frame is 'NEW' since 6.4. Previously both where > overlapping. > > Adding bibisectrequest more to get grasp of code area.. but well NISZ surely > better in assessing of this is worthwhile Probably not that helpful, but this was the change in 7.0. https://cgit.freedesktop.org/libreoffice/core/commit/?id=358f654af36fa12102685237f6eadebae4610fb5 author Tibor Nagy <nagy.tibor2@nisz.hu> 2020-05-20 13:31:51 +0200 committer László Németh <nemeth@numbertext.org> 2020-05-25 10:12:44 +0200 tdf#107119 DOCX import: fix parallel text wrap around frames
frame created by have the same <w:framePr> across a regular paragraph and a blockTable (a table not inside <w:p>). Good luck.
*** Bug 149370 has been marked as a duplicate of this bug. ***
From bug 69515, this looks useful: commit 874f0a1be443b8027d5aba2285866f31cf4169e5 Author: Cédric Bosdonnat on Mon Feb 18 17:34:06 2013 +0100 n#779642: ignore framePr inside table or the table import won't work
Dear Telesto, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7fddf33f70b5e496ca7e3936a845d47b9deca027 CPU threads: 8; OS: macOS 14.7.4; UI render: Skia/Raster; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded