Bug 429524 - The title bar of maximized windows is not blurred when using a transparent color scheme and blur enabled theme
Summary: The title bar of maximized windows is not blurred when using a transparent co...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: decorations (show other bugs)
Version: 5.20.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-22 21:45 UTC by Alessandro Astone
Modified: 2023-09-06 10:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Astone 2020-11-22 21:45:32 UTC
SUMMARY
When using the below described way of creating a blurred title bar, the blur effect is not applied to maximized windows.

STEPS TO REPRODUCE
0. Enable Blur in Desktop Effects
1. git clone https://github.com/KDE/breeze
2. cd breeze
3. wget https://gist.githubusercontent.com/aleasto/0d340bdba930ccc91be52c1e9039a3ed/raw/breeze-example.diff
3. git apply breeze-example.diff
4. [build and apply the theme in Window Decorations and Colors]

OBSERVED RESULT
Observe that, for example, Dolphin's title bar is translucent and blurred.
However, upon maximizing the window the blur effect disappears, and the title bar is now only semi-transparent.

EXPECTED RESULT
The title bar should be blurred even when the window is maximized

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 33
(available in About System)
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
If needed, I'm on: X11, proprietary nvidia
Comment 1 tromzy 2021-05-05 09:12:00 UTC
I can confirm this behaviour on Plasma 5.21.5 on Wayland (not tested on X11), with the Lightly window theme. Maximized windows don't get blurred titlebars, but unmaximized ones do.
Comment 2 David Edmundson 2023-09-06 10:38:42 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.