:: Forum >>

Tab indexing inconsistent, confusing

I'm using the UI package as a toolkit, and it's very cool. However, I'm having some problems with the tabIndex property which I thought should be brought to light:

1. input.js refers to the property as "tabindex" (lowercase "i") - everywhere else it's "tabIndex" (capital "I").

2. AW.UI.Inputs have a default tabIndex of -1. To change this, I can't simply call input.setTabIndex(1) or input.setAttribute("tabindex",1). Instead, I have to write input.getContent("box/text").setAttribute("tabindex",1). This is confusing - I dont want to have to know about AW.Templates.Input or AW.HTML.INPUT to use this property.

3. AW.UI.Labels have a default tabIndex of 1. Why would I ever want to tab into a label? Perhaps this has something to do with Label usage in the Grid...

What can we expect from the final 2.0 release in terms of the UI toolkit? I'm sure you're concentrating on the Grid, but my wallet is also quite interested in the polish of the UI package. Great job so far.
Monday, December 5, 2005
What I really want is a consistent way to set the tab index for any input element (Input, Combo, Radio, Checkbox, etc), and be able to unset it for non-input elements (Label, Tab, Fieldset, etc). It seems like the current defaults are the exact opposite of what I would expect when just creating inputs for a form.
Monday, December 5, 2005
I echo your concerns. I am doing testing right now and this bug popped up. There is a setTabIndex method now in Beta 4 but it does absolutely nothing from the end users point of view. I should be able to have 5 Inputs and set the exact order in which they can Tab around in the controls. Right now, when you hit Tab it takes you OUT OF THE FORM? It does go against the way standard HTML works.
Jim Hunter
Monday, January 30, 2006

This topic is archived.

Back to support forum

Forum search