Default contour is very tight. Seems the more common desire would be to have some space around an image. Shown here: https://youtu.be/w6Qcl-w7s5c?t=2m50s Older version but still applies.
Your video is off topic. Please attach a simple screen copy showing the problem. Set status to NEEDINFO, please, set it back to UNCONFIRMED once you have provided requested information. Best regards. JBF
Created attachment 117242 [details] No space by default
Which default value do you propose? Please, take into account that the unit may differ from a user to another. Best regards. JBF
It is pretty tight indeed (the mileage obviously varies with different images, but still). Anyone who has ever taken a book should perceive what a minimal margin should be. The current value should be doubled at least.
The current default is zero, so doubling it would not do much good. :) I would go with 0.10 inches which is shown as 2.54 mm, 0.25 cm, 0.60 pc, and 7.20 pt. Would not be bothered if each of those were doubled.
I suggest 2 mm default spacing. Maybe for LTR languages, that should be right of the image and for RTL left from the image?
Would be useful to use 1/8 (0.13) inches as that is one of the presets in the spacing drop down list in the sidebar and the default used in MS Word and Google Docs. This likely can be considered a duplicate of bug 87720.
Keep in mind if you increase the space you must also enable the control to adjust the space. It's disabled by default: https://bugs.documentfoundation.org/show_bug.cgi?id=102011
The control to adjust image margins is always enabled in the image dialog and in the sidebar.
Removing UX, please apply the suggestion in comment 7 with 1/8" (3mm when converted to SI). It sounds to me like an easyhack, please add the codepointers (NEEDINFO). Hard to say what topic/skill is needed. Jani?
Either this bug or bug 102011 should be closed as duplicates as the default margins would be set on the image, whether or not contour was enabled or not.
ok fine - let's close this one - the other has more info and such *** This bug has been marked as a duplicate of bug 102011 ***