[
https://issues.apache.org/jira/browse/WICKET-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Bille Jensen updated WICKET-957:
--------------------------------------
Fix Version/s: (was: 1.3.0-beta4)
1.3.0-beta5
> Change default focus component for focus related events to null
> ---------------------------------------------------------------
>
> Key: WICKET-957
> URL: https://issues.apache.org/jira/browse/WICKET-957
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Reporter: Carlos Pita
> Priority: Minor
> Fix For: 1.3.0-beta5
>
>
> Currently the default behavior for ajax requests is to restore focus on last
> focused element. This produces some bizarre situations when onfocus or onblur
> are used for ajax validation.
> For example, if the form component to be validated gets its focus transferred
> to some browser ui widget (say, the location bar), triggering an onblur
> validation this way, it immediately recaptures focus after validation has
> been completed (making it impossible to type text at the location bar unless
> your fingers happen to be faster than the ajax rtt, to follow the example). A
> similar problem occurs with tinymce editor, at least.
> This behavior can be circumvented explicitly setting
> target.focusComponent(null) for validation purposes, but why is it not this
> way in the first place, at least for the focus related events? With a better
> behaved default quite a number of ugly situations for such common use case as
> ajax validation is could be avoided.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
