Bug 292879

Summary: Invalid background of hover and focus state for ComboBox with custom native widget
Product: [Unmaintained] plasma4 Reporter: Michał D. (Emdek) <emdeck>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: adaptee, msx, pprkut
Priority: NOR    
Version First Reported In: 4.8.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Issue manifestation

Description Michał D. (Emdek) 2012-01-30 16:15:20 UTC
Created attachment 68339 [details]
Issue manifestation

Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

When Plasma::ComboBox is used with editable custom native widget, for example KHistoryComboBox then (starting with 4.8.0) initial background for focus and active states appears to have wrong width and is scaled so it appears as kind of gradient.
This happens until widget is resized.
This issue manifests in RunCommand applet (playground).

Reproducible: Always

Steps to Reproduce:
1. Run plasmoidviewer runcommand;
2. move mouse cursor over input or click it.

Actual Results:  
Background is invalid (pixmap width appears to be smaller than widget width)

Expected Results:  
Background pixmaps should be updated
Comment 1 Martín Cigorraga 2012-12-17 05:43:54 UTC
This is a live demonstration of this bug:

http://i.imgur.com/njgWu.png
http://i.imgur.com/FYpk5.png

As you see this probably happens because I have a very thin panel (something in the ~24px order).
Comment 2 Heinz Wiesinger 2013-02-09 14:59:47 UTC
I have the same issue still on 4.10
Comment 3 Michał D. (Emdek) 2013-04-05 06:48:50 UTC
It seems that spin box (week number) in calendar dialog used by clock applets (libplasmaclock) has the same issue.
Comment 4 Nate Graham 2018-06-08 19:44:45 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham