| Summary: | [Tree] hover background sometimes disappears | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Sternberg <rsternberg> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | tbuschto | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ralf Sternberg
It's better reproducible when moving the mouse from left (before the expand icon) to the right on the same item. Created attachment 200168 [details]
Poposed patch
This patch removes the check for hoverable in TreeRowContainer.js#_onElementOver. Tim, do you remember why this check was introduced? Is it save to remove it?
This was probably an attempt to prevent unnecessary re-renderings of the item. The flaw in this logic is that for an elementOut event is rendered (no hover), but then not for the elementOver (which would have hover again). I think it can be savely remoed. The propper fix would be to check if the old hover-element was hoverable too. Fixed in CVS HEAD as ivan suggested. This might create a very small performance loss when hovering treeitems, but improving tree performance will be a different task for the future. |