So I have a pretty basic WebDialogWindow that I'm showing in Modal mode, which contains an HTML table which in turn has some asp:Label and asp:Textbox controls; and below that there are OK and Cancel asp:Buttons.
The asp:TextBox controls have their TabIndex attributes set to incrementing values (1, 2, 3, 4, etc).
And in Chrome and IE8 I can tab between the textboxes fine.
BUT, in IE9, it doesn't work. Instead the first time I hit tab, the focus shifts to the buttons and then will never return to the textboxes above them.
When I look at the Source that's being displayed in the IE9 browser, the input tags for the textboxes do have the tabindex values set correctly.
SO, in summary:
The Tabindex works as expected in Chrome and IE8 for controls on a WebDialogWindow being displayed modally.
It doesn't work in IE9.
Thoughts?
Thanks!
Hello harmonk00,
Our developers have completed their review of development issue #75663. They have determined that this is not a bug for the following reasons:-DeveloperToolbar of IE shows correct tabIndexes after dialog is close. It just need to be refreshed.-WebDialogWindow has property to disable changes to tabIndexes ModalTabIndexes="false"
You can test it with the following code:
<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title></title> <script type="text/javascript"> function checkIndexes() { alert($get('Text1').tabIndex + ',' + $get('Text2').tabIndex + ',' + $get('Text3').tabIndex); } </script></head><body> <form id="form1" runat="server"> <div> <input type="button" value="check" onclick="checkIndexes()" /> <div> <input id="Text1" type="text" tabindex="1" /> <input id="Text2" type="text" tabindex="2" /> </div> <div> <input id="Text3" type="text" tabindex="3" /> </div> </div> <ig:WebDialogWindow ID="WebDialogWindow1" runat="server" Height="300px" Width="400px" Modal="true"> </ig:WebDialogWindow> <ig:WebScriptManager ID="WebScriptManager1" runat="server"> </ig:WebScriptManager> </form></body></html>
If you have more information regarding this issue that may require a reevaluation, or require further explanation, please let me know.
I have logged this behavior in our internal tracking system with a Development ID of 75663. I have also created support ticket: CAS-65369-9K46RH, so you will be notifed when it is fixed.