Description: FILEOPEN ODT: Moving image moves table to second page (only happening in ODT, not with DOCX/DOC/RTF) Steps to Reproduce: 1. Open the attached file 2. Click the bottom right image 3. Press arrow left 3x.. notice the flip flopping (caused by optimal wrap) 4. File Reload 5. Save AS DOCX/DOC 6. File Reload 7. Do the same image move -> This I would like to see Actual Results: DOCX/DOC and RTF after enabling Optimal wrap behave differently compared to ODT Expected Results: - Harmony in behavior as far as possible - In this case DOCX/DOC behavior Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: <buildversion> CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: ru-RU (nl_NL); UI: en-US Calc: CL
Created attachment 164106 [details] Example file
I see no difference between odf and docx. The same move. Tested in Version: 7.0.1.2 Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (ro_RO.UTF-8); UI: en-US Calc: threaded
(In reply to Telesto from comment #0) > Description: > FILEOPEN ODT: Moving image moves table to second page (only happening in > ODT, not with DOCX/DOC/RTF) > > Steps to Reproduce: > 1. Open the attached file > 2. Click the bottom right image > 3. Press arrow left 3x.. notice the flip flopping (caused by optimal wrap) Nothing happens, please re-test Arch Linux 64-bit Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 13aaeb5d148c1ea5163eecaa176fac4a67689277 CPU threads: 8; OS: Linux 5.12; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 7 May 2021
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp