Problem description: "Fill Format Mode" dosn't work. When I click "Fill Format Mode" button,Nothing happens. Steps to reproduce: 1. Start a Writer. 2. Open "Style and Formatting" dialog. 3. Click "Fill Format Mode" button. Current behavior: Nothing happens. Expected behavior: Enable "Fill Format Mode" and Image of the mouse pointer changes. On LibreOffice 4.2.x and master,this bug does not reproduce. Next command line will fix this bug. git diff libreoffice-4-1 master sfx2/source/dialog/templdlg.cxx | patch -p1 && make Operating System: All Version: 4.0.6.2 release
Complement: LibreOffice 4.0.6 has this bug. LibreOffice 4.1.3 has this bug. LibreOffice 4.2 or later does *not* have this bug.
Created attachment 90063 [details] ScreenShot 1(LibreOffice 4.0 or 4.1). I attach ScreenShot of "Style and Formatting"Dialog(LibreOffice 4.0 or 4.1). Nothing happens when click "Fill Format Mode" button.
Created attachment 90064 [details] ScreenShot 2(LibreOffice 4.2 or later). I attach ScreenShot of "Style and Formatting" Dialog(LibreOffice 4.2 or later). Enable "Fill Format Mode" when click "Fill Format Mode" button.
Created attachment 90067 [details] Patch for LibreOffice 4.1 This patch fixes the bug. This patch was created by next command line. $ git diff libreoffice-4-1 master sfx2/source/dialog/templdlg.cxx
Hello Tomofumi Yagi, I reproduce with LO 4.1.3.2 & Windows 7 Home Premium. I confirm this is not the case with LO 4.2.0.0.beta1 Build ID: f4ca7b35f580827ad2c69ea6d29f7c9b48ebbac7 and LO 3.6.6.2 portable.
(In reply to comment #5) Thanks for your comments - Jacques Guilleron, I think the following patch fixes this bug. "Related: fdo#67461 consider hierarchical view" ( author Caolán McNamara <caolanm@redhat.com> http://cgit.freedesktop.org/libreoffice/core/commit/?id=38b8e742872b2cbdba93f4d1b84c8f09b5ab38ff )
Created attachment 90301 [details] Cherry-picking-from-commit-38b8e742872b2cbdba93f4d1b84c8f09b5ab38ff I again attach a patch for LibreOffice 4.1.
I can confirm that the issue does no longer exist in LO 4.1.5 or 4.2 (but in 4.1.3). Therefore I believe it is time to close this bug as resolved.