Bug 420379 - Checkbox and its label move themselves to upper left corner when unchecked
Summary: Checkbox and its label move themselves to upper left corner when unchecked
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kconfig
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Matthew Dawson
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2020-04-21 13:47 UTC by Patrick Silva
Modified: 2020-04-21 18:22 UTC (History)
3 users (show)

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

Attachments
screen recording (1.22 MB, video/webm)
2020-04-21 13:47 UTC, Patrick Silva 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-04-21 13:47:00 UTC 
Created attachment 127746 [details]
screen recording

STEPS TO REPRODUCE
1. open Spectacle by pressing printscreen key
2. uncheck any checkbox
3. 

OBSERVED RESULT
Unchecked checkbox and its label move themselves to upper left corner of Spactacle window. They reappear in the correct place when I uncheck another setting.
Watch the attached screen recording please.

EXPECTED RESULT
unchecked setting should remain in the same place

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.1
Comment 1 Nate Graham 2020-04-21 17:07:15 UTC 
Can reproduce. I think this is a regression in the "show changed settings" feature.
Comment 2 Kevin Ottens 2020-04-21 18:06:25 UTC 
(In reply to Nate Graham from comment #1)
> Can reproduce. I think this is a regression in the "show changed settings"
> feature.

You're talking about a reverted patch which had no visible impact on that particular window. Please go fish somewhere else.
Comment 3 Nate Graham 2020-04-21 18:22:39 UTC 
Oh, I see you reverted the patch and I just hadn't rebuilt the kconfigwidgets framework yet. Now that I have, the problem in Spectacle disappears, so that patch did in fact cause this issue, just like I said.

Thanks for reverting it pending further discussion regarding how we integrate it. I'm sorry the feature's review process was frustrating, but there's no reason to be spiteful about it.