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. ***