Hello
I have problem with modal window opened by other modal window. Everything is displayed properly and working, but there is big problem with Tabs. They only working on Safari, but not on Firefox or IE.
I cannot go from one input (e.g, rad button or rad numeriktextbox) using Tab key on my keyboard on that browsers. Is there any way to solve that issue?
P.S. Rad buttons and rad numerik text boxes has client site scripts which are working as expected.
P.S.2 This both windows displays internal control. There is no external page redirect.
P.S.3 I'm using version 2010.3.1317.40
I have problem with modal window opened by other modal window. Everything is displayed properly and working, but there is big problem with Tabs. They only working on Safari, but not on Firefox or IE.
I cannot go from one input (e.g, rad button or rad numeriktextbox) using Tab key on my keyboard on that browsers. Is there any way to solve that issue?
P.S. Rad buttons and rad numerik text boxes has client site scripts which are working as expected.
P.S.2 This both windows displays internal control. There is no external page redirect.
P.S.3 I'm using version 2010.3.1317.40
2 Answers, 1 is accepted
0
Hi Marcin,
This behavior is expected and the correct way of functioning. When a modal RadWindow is opened, all the content below the modal overlay should be inaccessible and when a RadWindow is used with ContentTemplate, its content resides on the same page. As result, the first RadWindow takes all the elements on the page including the ones in the second window and sets their tabindex to -1 to make them inaccessible. The original tabindexes are restored when the window is closed.
To get the desired scenario and result, I can suggest the following approaches:
1. You could use a RadWindow with a specified NavigateUrl for the second window - in this manner the first one will not access its content elements - this is the better approach in case there are too many elements with tabindexes.
2. If there are not many inputs in the RadWindow content template you could utilize some JavaScript in order to set the desired tabindexes, for example when the second window is opened.
All the best,
Slav
the Telerik team
This behavior is expected and the correct way of functioning. When a modal RadWindow is opened, all the content below the modal overlay should be inaccessible and when a RadWindow is used with ContentTemplate, its content resides on the same page. As result, the first RadWindow takes all the elements on the page including the ones in the second window and sets their tabindex to -1 to make them inaccessible. The original tabindexes are restored when the window is closed.
To get the desired scenario and result, I can suggest the following approaches:
1. You could use a RadWindow with a specified NavigateUrl for the second window - in this manner the first one will not access its content elements - this is the better approach in case there are too many elements with tabindexes.
2. If there are not many inputs in the RadWindow content template you could utilize some JavaScript in order to set the desired tabindexes, for example when the second window is opened.
All the best,
Slav
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
0
Marcin
Top achievements
Rank 1
Veteran
Rank 1
Veteran
answered on 18 Jul 2012, 07:20 AM
Thank you for your answer. I will try with JavaScript.