Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328463 - [TableColumn Header] moveable columns lose and gain :hover state on single click
Summary: [TableColumn Header] moveable columns lose and gain :hover state on single click
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-22 08:29 EDT by Istvan Ballok CLA
Modified: 2012-07-13 04:16 EDT (History)
0 users

See Also:


Attachments
proposed patch for HEAD (3.20 KB, patch)
2010-10-22 08:34 EDT, Istvan Ballok CLA
no flags Details | Diff
fixed previous proposed patch (3.26 KB, patch)
2010-11-08 11:19 EST, Istvan Ballok CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Istvan Ballok CLA 2010-10-22 08:29:42 EDT
The problem
===========
Moveable columns lose and gain :hover state on single click - if the theme 
defines different background for the default and :hover states, 
this issue causes the TableColumn to blink on click.
You can easily reproduce this behaviour in the controls demo 
with business design.

Proposed resolution
===================
The :hover state should be removed from the TableColumn in javascript
only on the first mouse move event, after the mouse down event.
Comment 1 Istvan Ballok CLA 2010-10-22 08:34:05 EDT
Created attachment 181493 [details]
proposed patch for HEAD

The :hover state should be removed from the TableColumn in javascript	
only on the first mouse move event, after the mouse down event.
Comment 2 Istvan Ballok CLA 2010-11-08 11:19:07 EST
Created attachment 182632 [details]
fixed previous proposed patch

In the previous proposed patch, a local variable widgetUtil was not defined. 
I am sorry for that.
Comment 3 Ivan Furnadjiev CLA 2012-01-02 06:39:21 EST
This issue is still valid with 1.5M4.
Comment 4 Ivan Furnadjiev CLA 2012-07-13 04:16:44 EDT
This issue has been fixed with the recent refactorings on the Grid - see bug 383522.