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
restore focus on last focused element by default. But I'm also aware
that it causes problems with focus related event, so i think maybe we
should just call
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
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
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
Hi,
why is the default behavior for ajax requests to force focus into some
component (normally the one which triggered the event that caused the
request, I guess)? This produces some bizarre situations when onfocus
or onblur are used for ajax validation. For example, if the form
component to be
