Bug 364199

Summary: Background Contrast and Blur desktop animation causes desktop element overlay when using Zoom effect
Product: [Plasma] kwin Reporter: Justin Campbell <jtcmh13>
Component: effects-variousAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: major    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Actual results
Expected result

Description Justin Campbell 2016-06-11 03:40:18 UTC 
While the Background Contrast and/or the Blur desktop animation is enabled, UI elements from the desktop remain persistent on the screen regardless of the zoom level. By disabling both of these animations, it makes using the magnifier quite usable. However, this makes using transparent elements difficult as the text is no longer on a blurred background.

Reproducible: Always

Steps to Reproduce:
1. Have Plasma >=5
2. Have Background Contrast and/or Blur desktop animation enabled
3. Zoom in using kmag in fullscreen mode

Actual Results:  
See screenshot 1

Expected Results:  
See screenshot 2
Comment 1 Justin Campbell 2016-06-11 03:51:48 UTC 
Created attachment 99448 [details]
Actual results

A view of Konsole listing systemd unit files while zoomed in with the default bottom panel and application menu outlines displayed when those elements are not part of the magnified screen area.

It should be noted that the application menu was purposefully opened and does not always show on the screen. This was to demonstrate the problem.
Comment 2 Justin Campbell 2016-06-11 03:52:56 UTC 
Created attachment 99449 [details]
Expected result

A view of Konsole listing systemd unit files while zoomed in without Background Contrast or Blur desktop annimation enabled
Comment 3 Justin Campbell 2016-06-11 03:54:57 UTC 
I made a mistake in my original posting. The issue is not with kmag itself, rather the Zoom desktop animation.
Comment 4 Thomas Lübking 2016-06-12 12:46:19 UTC 

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