Description: RTF rendering fails to float the text around a shape despite \shpwr2\shpwr3 as part of the \shp block when surrounded by a table definition (\\trowd - \\row) placing the group for text with a shape within a table. Steps to Reproduce: 1.In an RTF file insert a text and a shape (e.g. with a picture) within a table using \trowd\trleft0\cellx9072\trql\intbl <picture> and <text> \cell\row 2.Open the RTF file using LibreOffice Writer Actual Results: Despite of the control sequence "\shpwr2\shpwr3" within the "\shp" block, the text will not flow around the shape. Expected Results: Because of the control sequence "\shpwr2\shpwr3" within the "\shp" block, the text is expected to flow around the shape on its left side according to the specs. In fact it asks for floating on the side with most space, which happens to be left in this case, but it does not change, if you explicitly asks for "left floating". Reproducible: Always User Profile Reset: Yes Additional Info: I have also tested this on the currently latest version (6.3.7.2) having the same result.
Created attachment 146905 [details] RTF file demonstrating missing floating text around shape This file demonstrates the two situations: - The first group of text below (starting "A.1") consists of some text and a shape (with a picture) where the text according to the specs correctly flows around the shape on its left side (as a result of the control sequence "\shpwr2\shpwr3" within the "\shp" block). - The second group of text below is exactly the same, apart from it has been surrounded by a table definition (\trowd-\row) placing the group for text with a shape within a table with one row and one cell. It also shows the same text and the same shape (with a picture), but despite of the control sequence "\shpwr2\shpwr3", within the "\shp" block, the text will NOT flow around the shape.
Seems like this is more of an import filter bug. Changing module to reflect that.
Neither MSWord, Apple Pages, nor Apple TextEdit display the image of the test file mentioned in the bug report. Testing with Version: 6.0.6.2 Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 Threads CPU : 4; OS : Mac OS X 10.14.1; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group confirms the reported beahviour.
Also reproduced with Version: 6.3.0.0.alpha0+ Build ID: 284dd58e326e61a5d84bde367e1e4873dd738c76 CPU threads: 4; OS: Mac OS X 10.14.1; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-11-22_23:09:13 Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded
Reproduced in Version: 5.3.6.1 Build ID: 686f202eff87ef707079aeb7f485847613344eb7 Threads CPU : 4; Version de l'OS :Mac OS X 10.14.1; UI Render : par défaut; Moteur de mise en page : nouveau; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Reproduced in Version: 5.3.4.2 Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3 Threads CPU : 4; Version de l'OS :Mac OS X 10.14.1; UI Render : par défaut; Moteur de mise en page : nouveau; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Verified that rendering is the same between macOS and Windows, so setting OS to all
Dear poul.steen, 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://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
Still repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 23f17b7ea6fbd2f422c7e40192ae60e4df25224c CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded Funny fact is modern MS Word just doesn't show images in the RTF file
Dear poul.steen, 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
Created attachment 191632 [details] LO 24.2 rendering Still an issue, added attachment to show current rendering Version: 24.2.0.0.beta1 (AARCH64) / LibreOffice Community Build ID: 5f390384195b7264c6e52add9e90a39790285249 CPU threads: 10; OS: macOS 14.2; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded