Bug 249665 - Panel should not auto-hide if any child widget is active
Summary: Panel should not auto-hide if any child widget is active
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: panel (show other bugs)
Version: 4.7.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-31 21:14 UTC by Leandro Glossman
Modified: 2018-06-08 18:23 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leandro Glossman 2010-08-31 21:14:59 UTC
Version:           unspecified (using Devel) 
OS:                Linux

Plasma panel should not auto-hide if any plasma widget contained inside is being shown. This works for some widget like the "Application Launcher", when displaying hidden icons in the "System Tray" widget or showing the digital clock calendar. But for some reason it doesn't work with most others widgets, e.g. notifications, networkmanagement applet, powermanagement and many more. It's really anti-aesthetic to watch the panel hide but some widgets to keep floating around.

Reproducible: Always

Steps to Reproduce:
Set the panel to autohide, then embed some widget, click on it and then unfocous the panel.

Actual Results:  
Panel autohide but widget remains opened.

Expected Results:  
The panel show be kept opened until the child widget is closed

Could this be an architectural problem in where the container applet have to know each child widget specifically to know how to handle specific situations. I dunno but I believe that some generic behaviour could and should be infered, like when a widget is active and being displayed.
Comment 1 Christoph Feck 2010-08-31 21:39:49 UTC
Confirmed. I long wanted to report this inconsistency.
Comment 2 Aaron J. Seigo 2010-09-01 01:00:26 UTC
there is architecture to support this; unfortunately, not all widgets comply and therefore cause issues.

if you can create a comprehensive list of the items that do not work, we can fix them one by one.
Comment 3 Christoph Feck 2010-09-01 02:24:37 UTC
I did not check all widgets, only those that I use, but that should get you started :) Thanks.

Works good:
+ Taskbar right click menu
+ Systray expander
+ Clock calendar expander

Needs to be fixed:
- Taskbar group menu
- Battery Monitor expander
- Weather Forecast expander (the one that I can select in systray settings)
- Device Notifier
Comment 4 Leandro Glossman 2010-09-01 16:12:27 UTC
...let me add...

Needs to be fixed:
- Notifications
- NetworkManagement
Comment 5 Kolia 2011-12-03 18:12:13 UTC
In kde 4.7.3 I can confirm this behavior at least for:
- Networkmanagement
- Device notifier
- Notifications

The battery and weather forecast widgets seem OK, even if to unfocus the panel I need to click somewhere in these cases.
Comment 6 Ian Schwarz 2014-04-19 08:58:08 UTC
This is still a problem in KDE 4.12.4.

(At least) the following widgets are broken:
- NetworkManager
- Device Notifier
- Battery Monitor
- (Veromix)
- (KDE Connect)

The following widgets are behaving correctly:
- Fuzzy clock
- K-Menu

The following widgets aren't behaving correctly (panel auto-hides), but the bottom corner is rounded and not cut off, so it's not as irritating:
- Notifications
- KDE System Tray - show additional icons
Comment 7 Ian Schwarz 2016-07-14 11:20:18 UTC
This used to be fixed in Plasma 5, but is now a problem again (reappeared somewhere between Plasma 5.6 and 5.7).
Comment 8 Fabian Vogt 2016-07-27 18:36:01 UTC
Confirmed on latest git master.
Launcher and calendar/clock work fine, but taskmanager entries and "status & notifications" don't.
Comment 9 Ian Schwarz 2016-10-11 23:16:26 UTC
Fixed in Plasma 5.8.0, at least.
Comment 10 Nate Graham 2018-06-08 18:23:37 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham