https://bugs.documentfoundation.org/show_bug.cgi?id=118230
--- Comment #4 from [email protected] ---
(In reply to Xisco Faulí from comment #3)
> Regression introduced by:
>
> author Samuel Mehrbrodt <[email protected]> 2016-07-05
> 12:05:28 +0000
> committer Samuel Mehrbrodt <[email protected]> 2016-07-05
> 19:58:48
> +0000
> commit fd6655080e181de4b78e31f13fe8ba35de8edfe5 (patch)
> tree b132314cd39e107b818f057cda33c07e6e9f2e47
> parent 28a03248b1d1649e157b788e43dfe8326f165379 (diff)
> tdf#73742 Don't replace existing image when inserting one
> If we want to replace an image, we have an entry in the context menu for
> that.
>
> Bisected with: bibisect-linux-64-5.3
>
> Adding Cc: to Samuel Mehrbrodt
I'm not entirely sure, but I suspect you're missing the point. It's not the act
of replacing the image that's the problem. It's where the replacement image
lands in terms of the top-down order of items on the document.
Currently, once the image is replaced, it always occupies the top-most position
in the hierarchy rather than honoring the placement of the position of the
picture which it replaced. That is the bug.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
