Bug 283396 - No blur effect on dashboard tooltips
Summary: No blur effect on dashboard tooltips
Status: RESOLVED DUPLICATE of bug 304564
Alias: None
Product: plasma4
Classification: Plasma
Component: dashboard (show other bugs)
Version: 4.7.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-05 15:43 UTC by Kai Uwe Broulik
Modified: 2012-08-05 14:44 UTC (History)
1 user (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 Kai Uwe Broulik 2011-10-05 15:43:38 UTC
Version:           unspecified (using KDE 4.7.1) 
OS:                Linux

When the dashboard is active there are no blur effects at all.
Neither the panels behind the dashboard are blurred, nor the tooltips of items.

Reproducible: Always

Steps to Reproduce:
Open the dashboard when Blur effect is enabled, look at the panel or hover over an item in e.g. folderview.

Actual Results:  
The background of especially the tooltips is not blurred making the contents hard to read

Expected Results:  
The background is blurred like on the normal desktop.
Comment 1 Martin Flöser 2011-10-05 16:01:50 UTC
Blur behind works fine. The tooltips are all inside the window, so we cannot really do anything about it in KWin. Because of that reassign to Plasma, though I fear they cannot do anything about it.
Comment 2 Kai Uwe Broulik 2011-10-05 20:14:35 UTC
The blur behind that blurs the entire screen in dashboard works fine (I deactivated it here due to performance) but the panel itself does not get blurred once the dashboard is above it.
Comment 3 Kai Uwe Broulik 2012-05-23 16:38:40 UTC
I know you know the interas better than I do but as far as I can tell, the tooltips on the Dashboard are also separate windows like the widget popups or tooltips outside the dashboard.
Comment 4 Janek Bevendorff 2012-08-05 14:44:30 UTC
Marking as a duplicate of Bug 304564 because that one contains more precise information.

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