Created attachment 168511 [details] A screen recording showing the bug using the Mendeley Toolbar add-on Steps to reproduce: 1. Install Mendeley (tested with Mendeley 1.19.4) 2. Open Mendely and click on Tools -> Install LibreOffice plugin 3. Open LibreOffice Writer. A new toolbar shows up on the top left corner 4. Right click on the new toolbar and clicks "Undock toolbar" 5. The toolbar is not undocked. Instead, the content of the Mendeley toolbar gets mixed up (superimposed) with the existing toolbar, creating confusion 6. The problem does not disappear by disabling the toolbar via View->Toolbars->Mendeley and re-enabling it via the same menu option 7. The problem DOES get fixed by closing LibreOffice Writer and re-opening again. Now the new toolbar is truly undocked An attached video capture shows the bug. Version: 7.0.3.1 Build ID: 00(Build:1) CPU threads: 12; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.0.3-0ubuntu0.20.10.1 Calc: threaded
Hello, what comment do you need?
I can confirm this exactly as described with another add-on toolbar: Zotero's. However, it's not limited to add-on toolbars. You can follow this steps with a default toolbar and end up with an overlap as well: Steps to Reproduce: 1. Open Writer 2. Right-click on Standard toolbar 3. Confirm that it is locked (the default) 4. Click on "Undock Toolbar" I can reproduce in recent versions as well: Version: 7.0.6.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Ubuntu package version: 1:7.0.6-0ubuntu0.20.04.1_lo1 Calc: threaded Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: adf65471e889676a600a9c6d0454c75cbd549ad3 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-13_04:44:18 Calc: threaded I am changing the title accordingly.
Created attachment 174446 [details] screenshot of issue with standard toolbar in LO 7.2.0.4 Screenshot of issue with version: Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
*** Bug 143704 has been marked as a duplicate of this bug. ***
repro STR in comment 2 (but using Bullets and Numbering toolbar) Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f8e11c6480ff0005715b989a6d4e2e10a3816cf6 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL Does this behavior appear before LO 7.0? (i.e., is it a regression?)
Additional information: To "unmix" 1. View > Toolbars > (unselect the mixed toolbar) 2. View > Toolbars> > (select the mixed toolbar)
Uncheck "View > Toolbars > [x] Lock Toolbars" to get rid of the overlapping toolbars. We should block the undocking feature in case a tb is locked.
This behavior may have started in 7.0. See bug 130163
(In reply to sdc.blanco from comment #8) > This behavior may have started in 7.0. See bug 130163 Rather bug 131817 as a consequence of bug 92484. And according bug 131441 the issue should be fixed...
Still reproducible with comment 2 steps in recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 10689e0f24e96781664e734fe23d109af6df77f1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
*** Bug 156960 has been marked as a duplicate of this bug. ***
(In reply to Heiko Tietze from comment #9) > (In reply to sdc.blanco from comment #8) > > This behavior may have started in 7.0. See bug 130163 > > Rather bug 131817 as a consequence of bug 92484. And according bug 131441 > the issue should be fixed... Unfortunately it is not fixed.
*** Bug 163744 has been marked as a duplicate of this bug. ***