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: So I've now gone through the slightly painful experience of implementing desterly's solution as noted in link above (and also by mbardon above) and rebuilt the AjaxControlToolkit from source. It works! Thank you desterly! If you've made you're way to this page, and have the same issue, I can safely say stop browsing for a short cut, download the source code and build the ACT yourself. I've spent most of yesterday evening and today looking for another solution, but not found anything. A few hints for building ACT if you've never done it before (like me): Go to "Source Code" and then "History". Select a change set/commit that has been downloaded lots of times before (I chose 31 Jan 2013 reference a2a6dc6854e0) and click on "Files". Have a quick read through the readme file and make sure the context is the correct commit/change set. Download the zip through the download option (top right). Unzip and open the solution in Visual Studio. Accept all the warnings and open project as normal. Set the build options to release and build the entire thing. In my case I had one error due to the website examples requiring ASP 4.5, so I excluded that project from the build and everything compiled fine. Look for the AjaxControlToolkit.dll after your build and use it in your project. Good luck - it's actually easier than I thought it would be. 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 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: So I've now gone through the slightly painful experience of implementing desterly's solution as noted in link above (and also by mbardon above) and rebuilt the AjaxControlToolkit from source. It works! Thank you desterly! If you've made you're way to this page, and have the same issue, I can safely say stop browsing for a short cut, download the source code and build the ACT yourself. I've spent most of yesterday evening and today looking for another solution, but not found anything. A few hints for building ACT if you've never done it before (like me): Go to "Source Code" and then "History". Select a change set/commit that has been downloaded lots of times before (I chose 31 Jan 2013 reference a2a6dc6854e0) and click on "Files". Have a quick read through the readme file and make sure the context is the correct commit/change set. Download the zip through the download option (top right). Unzip and open the solution in Visual Studio. Accept all the warnings and open project as normal. Set the build options to release and build the entire thing. In my case I had one error due to the website examples requiring ASP 4.5, so I excluded that project from the build and everything compiled fine. Look for the AjaxControlToolkit.dll after your build and use it in your project. Good luck - it's actually easier than I thought it would be. 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.