Yes, read about it at: http://www.w3schools.com/tags/att_global_tabindex.asp
IE Specific: http://msdn.microsoft.com/en-us/library/ie/ms534654(v=vs.85).aspx MDN: https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement.tabIndex Have a great day, Paul Bors > On Sep 22, 2013, at 11:23 AM, Tom Götz <t...@decoded.de> wrote: > > No, I don't have tabindex yet. Does this really help the browser in > determining the next tab? > > -Tom > > _ >> On 22.09.2013, at 09:54, Martin Grigorov <mgrigo...@apache.org> wrote: >> >> Hi, >> >> You can try with Chrome's Dev Tools - Timeline -> Events and Profile -> > CPU. >> Maybe one of those will show what is the reason. >> >> Do you have tabindex on the form elements ? >> >> >>> On Sat, Sep 21, 2013 at 11:21 AM, Tom Götz <t...@decoded.de> wrote: >>> >>> Hi! >>> >>> I've got a performance problem when navigating through form elements > using >>> the tab key. This issue is not directly wicket related, but maybe > someone >>> could point me into the right direction how to analyze/improve the >>> situation: >>> >>> we're using a tabpanel to render several tabs (~8-10) containing lots > of >>> form components. Tab-switiching is done client-side only, so there's no >>> ajax roundtrip. Now if you focus one of the form components and hit the >>> 'tab' key to skip to the next form element, there's a noticeable delay > of >>> ~200-400ms, although there's no ajax involved. Could this be related to > the >>> amount of form components displayed, i.e. does it take that long for > the >>> browser to calculate/determine which element to focus next? >>> >>> How could I determine the cause for the delay? >>> >>> Cheers, >>> -Tom > > > > <winmail.dat> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
