Hello,
We are manipulating the tab index of some form items to make sure that they can't be tabbed to when they are read only (canEdit set to false). To achieve this we also set the tab index to -1 (also the globalTabIndex) in code, this is based on a dynamic algorithm which uses values of the data record to decide if an item needs to be disabled or not. This means that the form is already drawn at the time wet set canEdit to false and assign the tab indexes to -1.
However, when we inspect the generated HTML and observe the tabbing behavior we notice that the -1 is not taken into account (original tab index is observed in the HTML). When we inspect the tabIndex and globalTabIndex on the form item using dev console we do see the -1 being set.
Doing explicit reDraw calls on the formitem seem to have no effect.
How can we get the -1 to be taken into account in this scenario?
This is on v8.3p_2013-05-29/Pro Deployment (built 2013-05-29).
thanks!
We are manipulating the tab index of some form items to make sure that they can't be tabbed to when they are read only (canEdit set to false). To achieve this we also set the tab index to -1 (also the globalTabIndex) in code, this is based on a dynamic algorithm which uses values of the data record to decide if an item needs to be disabled or not. This means that the form is already drawn at the time wet set canEdit to false and assign the tab indexes to -1.
However, when we inspect the generated HTML and observe the tabbing behavior we notice that the -1 is not taken into account (original tab index is observed in the HTML). When we inspect the tabIndex and globalTabIndex on the form item using dev console we do see the -1 being set.
Doing explicit reDraw calls on the formitem seem to have no effect.
How can we get the -1 to be taken into account in this scenario?
This is on v8.3p_2013-05-29/Pro Deployment (built 2013-05-29).
thanks!
Comment