| Summary: | Problem with hover state and animations | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Sternberg <rsternberg> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 1.3 | ||||||
| Target Milestone: | 1.3 RC1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ralf Sternberg
Created attachment 166927 [details]
fix
What happend:
AbstractButton uses animation.cancel() if the change in backgroundColor/gradient is not to be animated. Usually, the animationRenderer detects this and renders the new value without delay. However, if the animation is already running, no such check existed and the changes were not rendered.
Solution:
Introduced check in AnimationRender#onOriginalRenderer. Also some minor changes to AnimationRender#renderValue to better test for the endResult of a canceled animation. Tests updated.
Commited patch to CVS HEAD. |