Bug 37560 - Removing all toolbars does not remove its background
Summary: Removing all toolbars does not remove its background
Status: RESOLVED DUPLICATE of bug 36475
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.4.0 RC1
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 18:13 UTC by Lars Knickrehm
Modified: 2011-05-24 23:21 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
I just hovered the menu entry I used to hide the toolbar. The toolbar's blank background's left afterwards. (7.88 KB, image/png)
2011-05-24 18:13 UTC, Lars Knickrehm 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Knickrehm 2011-05-24 18:13:55 UTC 
Created attachment 47115 [details]
I just hovered the menu entry I used to hide the toolbar. The toolbar's blank background's left afterwards.

LibreOffice has at least two different ways to show and hide toolbars. Using the "View" > "Toolbars" menu is working quite well, but hiding a toolbar using it's contextmenu does not remove the background of the toolbar.
I just attached two images. One showing a toolbar's contextmenu () and a second showing the blank background after hiding.
Comment 1 Rainer Bielefeld Retired 2011-05-24 22:33:00 UTC 
[Reproducible] with "LibreOffice 3.4.0RC1  – WIN7  Home Premium  (64bit) English UI [OOO340m1 (Build:11)]". When you close the last docked toolbar in a line using context menu, the bar where the toolbar has been docked will not disappear as it does if you undock toolbar or make it invisible using menu 'View > Toolbars').

I remember we had something similar reported for the find bar,but I can't find the report.
Comment 2 clio 2011-05-24 23:17:06 UTC 
Reproducible with LibO 3.4 rc1 on Ubuntu 10.04 x86
Comment 3 vitriol 2011-05-24 23:21:24 UTC 

*** This bug has been marked as a duplicate of bug 36475 ***