Bug 340009 - Background contrast geometry is not updated
Summary: Background contrast geometry is not updated
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (other bugs)
Version First Reported In: git master
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-15 21:32 UTC by Kai Uwe Broulik
Modified: 2018-08-25 16:02 UTC (History)
2 users (show)

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


Attachments
Background contrast area not updated (107.41 KB, image/png)
2014-10-15 21:32 UTC, Kai Uwe Broulik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2014-10-15 21:32:08 UTC
When the dialog size changes, the background contrast region is not updated properly. Blur is, however. When moving around the dialog, it is updated eventually.

Reproducible: Always

Steps to Reproduce:
1. Right click digital clock (or kickoff or taskmanager)
2. Choose "Alternatives"
3. Alt+Right click the resulting Alternatives dialog and make it bigger

Actual Results:  
The blur region grows with the dialog, the background contrast does not

Expected Results:  
Both regions stay in sync with the dialog size
Comment 1 Kai Uwe Broulik 2014-10-15 21:32:46 UTC
Created attachment 89155 [details]
Background contrast area not updated
Comment 2 Martin Flöser 2014-10-16 06:01:05 UTC
Adding Marco as the Background Contrast Effect expert.

@Kai Uwe: could you please look on the xproperties, whether they change when the dialog size changes.
Comment 3 Kai Uwe Broulik 2014-10-16 09:08:17 UTC
I just ran xprop over the original dialog and the resized one and the files are identical (even the blur behind region property)
Comment 4 Vlad Zahorodnii 2018-06-04 22:28:56 UTC
It's been ~4 years since last comment, does this bug still persist?
Comment 5 Vlad Zahorodnii 2018-08-25 16:02:44 UTC
If you're still able to reproduce this bug, please reopen it.