| Summary: | [FocusEvent] notifies listeners in wrong order | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Austin Riddle <austin.riddle> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Flags: | rsternberg:
review+
|
| Version: | 1.5 | ||
| Target Milestone: | 2.0 M1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | sr151 | ||
Fixed in master with commit 44a85a9a7964e6daa918fccdaf00da9541a46655. I will suggest to backport this fix to the 1.5 maintenance branch too. +1 to backport this fix to 1.5. Applied to 1.5 maintenance branch with commit a660922a1e6aba08d624fa5f3a984f2eb0cf93ed. |
In HEAD, Focus listeners between controls are notified in the wrong order. This is reproducible using the controls demo: 1. Go to the focus tab and click in the first text control 2. Hit the tab key or click in the next text control The log shows: focusLost: Text{} focusGained: Text{} focusGained: Text{} Expected behavior is: focusGained: Text{} focusLost: Text{} focusGained: Text{}