Check with Firebug or Dev tools which component is focused before the Ajax call (see the request headers) and later after the processing of the Ajax response check whether there is an element with such id in the DOM tree.
On Mon, Apr 16, 2012 at 10:36 AM, Tom Eugelink <t...@tbee.org> wrote: > > Thanks for the feedback. > > So to check if this is the cause, I could simply remove the ajax code. > > Tom > > > > > On 2012-04-16 08:54, Martin Grigorov wrote: >> >> Hi Tom, >> >> Wicket keeps track of the last focused element only for Ajax requests. >> I.e. Wicket sends a header in the ajax requests with the id of the >> focused element when the Ajax call starter and later when the Ajax >> response is processed it re-focuses this element. >> Additionally there is AjaxRequestTarget#focusComponent(Component) >> method which may be used to focus another element. >> >> If you replace the focused element in the Ajax response then >> lastFocusedId will be obsolete and Wicket wont be able to find the old >> component. >> >> I hope this helps you find out what causes the jumps in the focused >> elements. >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
