https://bugs.documentfoundation.org/show_bug.cgi?id=137920
Timur <gti...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vmik...@collabora.com
Keywords|bibisectRequest |bibisected, bisected
--- Comment #12 from Timur <gti...@gmail.com> ---
Lin 64 commit d250ca91c79f457102daf4da81446b7f130fb0ee
Date: Fri Dec 6 01:56:32 2019 +0100
source sha:d0aa2dbdf37aefe5b8d096fc5ea50cd13f87c5b0
pre source sha:f96f290c1988d7bfbe439470281d946d6f5add65
author Miklos Vajna <vmik...@collabora.com>
sw: insert image: set anchor to at-char by default
This changes the default set in commit
4f40bf6a79de6d60da0a5090cdfeda6242e889f0 (sw: insert image: set anchor
to as-char by default, 2019-07-04), to have a better compromise, taking
both Word defaults compatibility and usability into account.
The problem is that users are used to just inserting an image and being
able to drag it to its final location, which is broken with as-char
anchoring.
So default to at-char anchoring, this is still something that is fully
interoperable to Word (unlike the old to-para anchoring), but allows the
easier image move again.
(cherry picked from commit a7528cd6f17ea5c5b29e7d607e54c62de0d9e7db)
CC: Miklos, please see.
--
You are receiving this mail because:
You are the assignee for the bug.
