Dunno. Up till now my workaround is to set focusComponent to null at the server-side for validation purposes. I'm not suggesting that this should be wicket's approach or something similar, of course.
Regards, Carlos On 9/11/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > see my comments in that issue. > Its not that we have to do something on the serverside this is a clientside > issue. > > johan > > > On 9/11/07, Carlos Pita <[EMAIL PROTECTED]> wrote: > > > > > behavior if the event is onblur. Can you submit RFE? > > > > Done. I filed it as minor improvement > > https://issues.apache.org/jira/browse/WICKET-957. > > > > > Because currently there is no way during ajax processing to determine > > > that the event was a focus related one. I think that it's good to > > > > Maybe setting focusComponent to null by default for any > > AjaxEventBehavior whose event happens to be onblur or onchange will be > > enough. Even if done at the AjaxFormComponentUpdatingBehavior imo this > > will be a great relief for people who are implementing their first > > wicket ajax-validated forms and haven't a clue about the cause of such > > a strange focus behavior that suddenly possesses their browsers. > > > > Regards, > > Carlos > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
