https://bugs.documentfoundation.org/show_bug.cgi?id=166782
--- Comment #5 from Telesto <[email protected]> --- (In reply to Mike Kaganski from comment #3) > I remember it was explicitly requested and implemented. Why do you file this > as a problem? I have not by definition problem with being able to set padding explicitly without border. A) It started with DOCX export of a shape with padding: padding is gone(and image increased in size). Which actually in relation to bug 166783. B) Bug 166783: padding is not added to the image, but the image will reduce in size equal to the padding. C) Which landed me here. I interpret 'padding' in context of border as "border padding", not as "borderless padding". So I configured padding as a sub-setting of border; not as independent property I wanted to 'undo' the shrinking of the image manually (so not using undo). I expected disabling the border to undo image size reduction. Which isn't insane expectation: as this was how it worked before LibreOffice 5.3 So the issue is 'padding' has become ambiguous. In the sense it can mean: border padding or borderless padding. So you start applying padding in context of borders. You want to disable the border, and now is assumed you want to have 'borderless padding', instead of no border and no padding. Connection between border and padding being dropped Borderless padding has nothing to do with 'borders' in the strict interpretation. It doesn't belong to the 'border' tab anymore. In the more extensive interpretation you can say: well padding is a border around an image :-). So it's fitting. And it does the same as before. Except the connection being dropped. Which obviously being true I'm currently not having a clear idea how to un-entangle 'borderless padding' from border padding. Maybe a checkbox on the border tab similar to 'synchronize' called 'borderless padding', unchecked by default. So disabling a borders would disable padding, except when borderless padding being checked. This would be more communicative UI-wise and reduce surprises. -- You are receiving this mail because: You are the assignee for the bug.
