Bug 219228 - Compositing effects are not applied to windows using own window decorations
Summary: Compositing effects are not applied to windows using own window decorations
Status: RESOLVED DUPLICATE of bug 157353
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-18 19:54 UTC by Craig Cabrey
Modified: 2009-12-18 20:04 UTC (History)
0 users

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 Craig Cabrey 2009-12-18 19:54:09 UTC
Version:            (using KDE 4.3.4)
Compiler:          gcc 4.4.2 
OS:                Linux
Installed from:    Archlinux Packages

When an application uses window hints to use its own window decorations, a shadow is not applied to the window. This makes the application look out of place and sometimes leaves visual artifacts on the screen. A prime example of such an application is Chrome and/or Chromium. Not sure if this is a Chrome/Chromium bug it happens with Compiz as well or if it is just the nature of the app, but it would be great if this was fixed.

Loaded plugins:
Fade, Login, Minimize Animation, Shadow, Slide, Taskbar Thumbnails, Desktop Grid
Comment 1 Martin Flöser 2009-12-18 20:04:01 UTC
Applications like Chrome shouldn't draw their own decorations. The use case for own decorations is very limited like for example Yakuake. KWin (and as you see all other composited window managers) can't know how the window looks like and by that a proper shadow can't be applied. Instead of painting a totally broken shadow it's better to not draw any shadow.

I do not understand why Google is going the way of implementing own decorations. This breaks the consistency desktop environments provide be it KDE Plasma, Gnome or any other system. But that isn't the only "strange" move of Chrome (see http://spot.livejournal.com/312320.html).

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