Steps how to reproduce with Installation of Version:7.2.1.2 (x64); Build ID: 87b77fad49947c1441b67c559c339af8f3517e22; CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI: de-DE; Calc: threaded | my default User Profile: 0. From Test kit open "NewSample.odt" 1. From WIN Files Explorer drag and drop "field-kitchen-1714153_1920_small.png" To most top table Expected: row hight adapted to picture hight Actual: row height keeps as it is 😥 For next test close writer without saving 10. From Test kit open "NewSample.odt" 11. From WIN Files Explorer drag and drop "field-kitchen-1714153_1920.png" To most top table Expected: row hight adapted to picture hight Actual: as expected 👌 a) Vague suspect: Problem from (1) has to do with relation between picture width and table column width. Additional tests: If you redo test from step 0, but drag and drop to left cell of second table, row height will be adapted. That underpins my suspect. Close writer without saving and 20. From Test kit open "NewSample.odt" 21. From WIN Files Explorer drag and drop "chicken_small.jpg" To most top table Surprise: row hight adapted to picture hight ⁉ b) Related to different handling between .jpg and .png. Both sampeld pictures have 640 px width
Created attachment 176399 [details] Test kit
This one probably is related to Bug 145807 or even is the root of tht one.
I confirm it with Version: 7.2.4.1 (x64) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL I agree with your theory, Rainer. If you increase the size of the picture after you additional test and drag it to the top table, it works (width of the picture is more or less wifht of the table cell.
Perhaps related to bug 105302 (had no time to check it)
Dear Rainer Bielefeld Retired, 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