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

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|bibisectRequest             |bibisected, bisected
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=14
                   |                            |9431
      Regression By|                            |xuenhua
            Version|7.4.7.2 release             |7.4.0.3 release
                 CC|                            |heiko.tietze@documentfounda
                   |                            |tion.org,
                   |                            |[email protected]

--- Comment #7 from Stéphane Guillou (stragu) 
<[email protected]> ---
With steps from comment 6 and the linux-64-7.4 repo, I bibisected it to first
bad commit 837ba694d276705ecac2999951615c7d3c41d4e3 which points to core commit
334b44affe24340f44216021a4699699dd5dde96 which is a cherrypick of:

commit  0ec2b93c28093c80572c43f7be261630bd85f232
author  xuenhua Wed Jun 01 15:29:49 2022 +0800
committer       Caolán McNamara Fri Jun 17 20:52:05 2022 +0200
tdf#149431 Fix the sidebar's width
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/135220

Bug 149431 was marked a duplicate of bug 128180: "Allow each deck to keep its
own width in the sidebar".

So as I understand it: the test case of bug 149431 (moving to a wider deck
affects the width of the previous deck) is indeed fixed, but we lost the
persistence of a deck wider than the minimum widthf after a reload.
Best example of why this is problematic is probably the Gallery deck: the user
might want to always show 4 columns of objects. It is reset to 2 columns after
a reload.

Enhua, can you please have a look?
Heiko, you've followed the Sidebar width conversation in more detail than me,
copying you in in case you have input :)

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

Reply via email to