| Summary: | [Text] setFocus does not work under some constellation | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | David Casas <david.kasas> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | rsternberg, sgouta2, tbuschto |
| Version: | 1.5 | ||
| Target Milestone: | 2.0 M1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | sr152 | ||
|
Description
David Casas
Change the priority to P1 as this is a regression. The underling input field does not gain the focus, because in BasicText.js#_visualizeFocus qx.event.handler.FocusHandler.blockFocus is true. Reproducible with Examples Demo and Controls Demo -> Dialogs under all browsers but Chrome. If I remove the animation from Shell-DisplayOverlay the problem is gone. I suspected this also. The focus should be set after the animation finished, not yet sure why that doesnt happen. So... for now (and RAP 1.5) the workaround is to set the Shell-DisplayOverlay animation to none:
Shell-DisplayOverlay {
animation: none;
}
Yo can leave the animation out and it is working fine too...at least on firefox animation: fadeOut 400ms ease-out; Cheers Fixed with commit b6504e2c21733c44ea69241b46a049a0583cdf38. There was a mechanism in place that was supposed to set the focus after the appear animation was done. This was meant for a shell appear animation, not the overlay. While trying to fix the issue, i realised that the entire mechanism was way to error-prone for such a cosmetic feature, so i removed it. Focus is now set at once. As a result, it's now theoretically possible to interact with a shell that's not yet fully visible. *** Bug 387179 has been marked as a duplicate of this bug. *** +1. I think that the fix is safe to be backported to 1.5 branch. +1 Backported to 1.5-maintenance branch with commit 9ddaa4c7607321754471c8723bf852fd49595ddf. |