https://bugs.documentfoundation.org/show_bug.cgi?id=129126
Terrence Enger <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #5 from Terrence Enger <[email protected]> ---
Created attachment 156317
--> https://bugs.documentfoundation.org/attachment.cgi?id=156317&action=edit
bibisect-linux-64-6.5, tail of terminal output
Working on debian-buster in bibisect-linus-64-6.5, I see:
commit s-h seq date
-------- -------- ------ -------------------
good 8410d885 83edee30 516511 2019-11-18 16:36:04
bad 135aa137 a7528cd6 516513 2019-11-18 16:37:13
The bad commit is (lines rewrapped) :
commit a7528cd6f17ea5c5b29e7d607e54c62de0d9e7db
Author: Miklos Vajna <[email protected]>
Date: Mon Nov 18 13:50:32 2019 +0100
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.
Change-Id: Ibc61ae167fc9e5cc31b04c83e854556309e27fd4
Reviewed-on: https://gerrit.libreoffice.org/83089
Reviewed-by: Miklos Vajna <[email protected]>
Tested-by: Jenkins
I am removing keyword bibisectRequest and adding keywords bibisected,
bisected.
--
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
