https://bugs.kde.org/show_bug.cgi?id=444244
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |NOT A BUG
CC| |k...@davidedmundson.co.uk
--- Comment #1 from David Edmundson <k...@davidedmundson.co.uk> ---
>I guess it is because the application or element has to specially request blur
>effect to be applied by kwin
That's correct. We also have the contrast effect which is similar and with
extra metadata that has to come from the client.
I don't personally trust that just blurring all non-opaque regions will be
without regressions in random clients as we take control away from them.
>I doubt a solution would be even possible without being significantly
>integrated into kwin.
There is an existing proposal to allow the kwin rules to do this. That would
work for both this case and X11 (and be far less horrible than users running a
shell script). Effects already have a code path to read from window properties
for the InternalWindow, so we can "just" have a rule set them.
--
You are receiving this mail because:
You are watching all bug changes.
