Bug 6275 - gtk+ sometimes don't render expanders when mouse is over
Summary: gtk+ sometimes don't render expanders when mouse is over
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Low normal
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2012-06-01 10:28 CEST by Thierry Vignaud
Modified: 2015-05-19 16:21 CEST (History)
0 users

See Also:
Source RPM: gtk+2.0
CVE:
Status comment:

Attachments
expander is rendered as mouse cursor went over it (8.09 KB, image/png)
2012-06-01 10:29 CEST, Thierry Vignaud 		Details
expander is not rendered as mouse cursor went over its text instead of its icon when moving back to the view line (8.31 KB, image/png)
2012-06-01 10:29 CEST, Thierry Vignaud 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Thierry Vignaud 2012-06-01 10:28:27 CEST 
gtk+ sometimes don't render open expanders when mouse is over,
eg in services list in summary
See attached screenshots

when mouse cursor is moved over the expander line, the expander will:
- be drawn if mouse cursor land over it
- not be drawn if mouse cursor land over text
Thierry Vignaud 2012-06-01 10:28:44 CEST

Keywords: (none) => USABILITY
Priority: Normal => Low

Comment 1 Thierry Vignaud 2012-06-01 10:29:14 CEST 
Created attachment 2411 [details]
expander is rendered as mouse cursor went over it
Comment 2 Thierry Vignaud 2012-06-01 10:29:41 CEST 
Created attachment 2412 [details]
expander is not rendered as mouse cursor went over its text instead of its icon when moving back to the view line
Thierry Vignaud 2014-07-11 13:58:40 CEST

Assignee: bugsquad => olav
Source RPM: (none) => gtk+3.0

Comment 3 Thierry Vignaud 2015-05-19 16:21:10 CEST 
this was gtk+2.0, we've switched to gtk+3.0 since and then to a new theme

Status: NEW => RESOLVED
Resolution: (none) => OLD
Source RPM: gtk+3.0 => gtk+2.0
Note You need to log in before you can comment on or make changes to this bug.