https://bugs.documentfoundation.org/show_bug.cgi?id=139264

Buovjaga <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|bibisectRequest             |bibisected, bisected
                 CC|                            |ilmari.lauhakangas@libreoff
                   |                            |ice.org
      Regression By|                            |Kohei Yoshida
            Summary|Footnote Separator line     |The dash count of footnote
                   |dashes fuzz and unfuzz      |separator lines change
                   |depending on zoomlevel      |depending on zoom level

--- Comment #7 from Buovjaga <[email protected]> ---
Bibisecting with Linux 43max, there was also an intermediate state where the
line was dashed differently than originally, but did not change when zooming.
When marking it as bad, there were a lot of bad commits to skip. The range was

https://git.libreoffice.org/core/+log/9e18f7e3cfec960b788eb5df3b53daf9efd092ab..f2ff3b10547a7a3f31a8dd885a004e5f4bec1377
where I assume the change is f2ff3b10547a7a3f31a8dd885a004e5f4bec1377
Pass scaling to borderline primitive objects.

...which is runnable in the repo.

Then, bibisecting with that one as good and latest as bad, I got an exact
commit explaining our current state:
0a8ddb61b1178a7ab48de7aa3383cea4c4c1774c
Apply dashing without consulting current map unit.

Using scaling is sufficient.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to