Apache OpenOffice (AOO) Bugzilla – Issue 76398
Settings on the image frame style lost when caption is applied
Last modified: 2007-04-16 16:01:13 UTC
Steps to reproduce the issue: In a new Writer document, edit the "Graphics" frame style in order to add space below any inserted image. Insert dummy text and in between it insert an image. When the image is inserted, the spacing works as expected. Now, right click over the image and select "caption". Enter any text and press enter. Expected behavior: the space set in the Graphics frame style keep a distance between the image and the caption. Result: the space below the image is transferred to the new external frame and no space is left between the image and the caption. Below the external frame a space NOT set by the user is inserted while the configured space below the image is lost. Notice: By re-applying the Graphics frame style to the image only, the space is recuperated. Everything behave as if direct formating were applied to both, Graphics and "external" frame style reverting the spacing settings introduced by the user. In fact, the frame where the image and the caption is inserted is a variation of he "Frame" frame style, but with "direct formatting" applied on it: There is no way to control the default properties of that frame. Up to the moment, the only way to have a well defined "caption environment" is to define it by hand, making the whole built-in captioning system useless. Suggestion: when a caption is inserted, a new frame style must be created (maybe based on the Graphics frame style, or maybe the same Graphics frame style) and applied to the external frame without changing the properties of the original frame. The change is not a great one and will give to the user more control over the process.
Already tracked as issue 23957. *** This issue has been marked as a duplicate of 23957 ***
Closing duplicate.
Even if they are similar, the description here address (IMHO) the root cause and propose a possible solution. May I insists?
That's right, but we will close newer issues in favor for older ones. This keeps issue handling much more convenient. Thanks for you patience. Feel free to add your comment in issue 23957. The developer will of course fix the root cause though it is not mentioned in the description. *** This issue has been marked as a duplicate of 23957 ***