If I have a floating image, and I "Insert Caption" on it, what I expect is absolutely no change in the wrapping below or to the sides, no right-to-left movement of the image, but only a small(ish) push-down at the bottom which may result in more wraparound of text, in which we see the footnote text. And - if this is achieved using a new frame, then that frame should inherit the image's wrapping and space around properties with the image itself losing them. Instead, I observe some or all of the following: * Resizing * Movement of the image relative to its original position, even when that's not necessary * Extra padding, or under-padding * More surrounding space than the image had before
Eyal, this enhancement request is similar to the problems described in your report in bug 147757. So what is different? And why do we need this enhancement request (for me every problem you mention should be treated like a bug). => NEEDINFO
It may be true that I mixed up some of the effects of that bug with this one. But - that bug is about the frame not corresponding to the image at all; here, even if the dimensions do correspond more properly to the image, we still get, at the very least: * Movement of the image relative to its original position * Extra empty space above the image and that shouldn't happen.
[Automated Action] NeedInfo-To-Unconfirmed
I can only confirm empty space between top caption border and image. I would consider this as a bug. So I suggest to focus this report on that specific problem. Do you agree?
(In reply to Dieter from comment #4) > I can only confirm empty space between top caption border and image. I would > consider this as a bug. So I suggest to focus this report on that specific > problem. Do you agree? Sure.
(In reply to Eyal Rozenberg from comment #5) > Sure. So I've changed bug summary and set status to NEW. But - very strange - I could only confirm with your attachment 178648 [details] from bug 147757. Even if I remove the image and direct formatting it is still reproducible.
*** Bug 152302 has been marked as a duplicate of this bug. ***
Dear Eyal Rozenberg, 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
Bug still manifests with: Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3e9658a201f60dee95bd1bd8421b18bf8905c308 CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US