Hi,
I found an error in Tabs of ajax control toolkit, I have downloaded the last version of June 2012 Release, the erros occors in the other versions too.
The error consist in have a TabContainer inside a Tab of other TabContainer, inside an update panel.
When run the application an error of "Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus."
The error occors only in the IE 8, I dont have IE 7 for test. The error dont occors in IE 9 compatibility mode.
I have resolved this error, add a try/catch block in js script "Tabs.pre.js" where the focus of tab is set.
Attachment the application that occors the bug.
Ivan Patrick.
Comments: > I guess the smart folk at AjaxControlToolkit don't want to use a try without a proper catch, but it would be good to get the issue fixed once and for all. Ignoring a bug is in my opinion a lot worse than an ugly workaround. I couldn't agree more. I've encountered another bug that goes hand-in-hand with this one on the meantime. I also had trouble building the solution when I added the toolkit to our local Source Control.
I found an error in Tabs of ajax control toolkit, I have downloaded the last version of June 2012 Release, the erros occors in the other versions too.
The error consist in have a TabContainer inside a Tab of other TabContainer, inside an update panel.
When run the application an error of "Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus."
The error occors only in the IE 8, I dont have IE 7 for test. The error dont occors in IE 9 compatibility mode.
I have resolved this error, add a try/catch block in js script "Tabs.pre.js" where the focus of tab is set.
Attachment the application that occors the bug.
Ivan Patrick.
Comments: > I guess the smart folk at AjaxControlToolkit don't want to use a try without a proper catch, but it would be good to get the issue fixed once and for all. Ignoring a bug is in my opinion a lot worse than an ugly workaround. I couldn't agree more. I've encountered another bug that goes hand-in-hand with this one on the meantime. I also had trouble building the solution when I added the toolkit to our local Source Control.