This project is read-only.


Problem with tabcontainer in IE8


My team and me have developped a control using some ajax controls... The main control used is the tabcontainer containing 2-3 tabPanels.
Our control is working perfectly in ie9, firefox, chrome, opera but is not working with ie8. I've tried multiple version of AjaxControlToolkit .NET 3.5 library (Nov. 2011, May 2012, June 2012) expecting each time that this bug has been fixed but the error is still there.

The error is the following one:

Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus

file attachments

Closed Dec 14, 2013 at 2:39 AM by Superexpert


kunal0701 wrote Jul 25, 2012 at 3:59 PM

Hi bisseins,

You are right. The issue still seems to be there. The solution provided by desterly in resolves the issue.

Attached is the updated dll of June 2012 release

Tommark wrote Aug 2, 2012 at 5:37 PM

Please incorpertate this fix into the next version of AJAX Toolkit, it is currently preventing us from using the latest version in our project.

Tommark wrote Aug 7, 2012 at 4:47 PM

incorpertate = incorporate, I couldn't spell last week apparently..

fray2200 wrote Sep 10, 2012 at 10:51 PM

I have just encountered this as well. I'm using the most recent v3.5.

MarjaR wrote Sep 27, 2012 at 1:51 PM

The DLL which can be downloaded here seems t be compiled against .NET 2.0? Is that correct?

I need a 4.0 DLL with this IE8 fix.
Can anyone provide that? Thanks in advance!

ivanpfontanive wrote Sep 27, 2012 at 3:49 PM


I found the error too, and i resolved downloading the code and add try/catch block in script.

See the post.


Ivan Patrick

uberDoward wrote Oct 5, 2012 at 6:05 AM

Noting this error still exists in September 2012 release. Try/catch block fixed it per desterly. Hoping maintainers will add the fix to the next release.

brandonaho wrote Dec 20, 2012 at 5:12 PM

Does anyone have a DLL already built with the fix for the tabs that I can download or is there another work around for IE8 and nested tabs?

deggen wrote Feb 12, 2013 at 4:38 PM

We're still seeing this issue on version

Kartris wrote Apr 30, 2013 at 9:34 AM

We fixed the latest code (as of date of this post) and compiled the DLL for ASP.NET 4.0. I tried to upload to this thread, but the spinner just sits there for 15 mins. So instead, grab the DLL from our repository (Bin folder):

Or from our web site:

lovekumars wrote Dec 31, 2013 at 4:34 AM

Thank you Kartris!
This issue still exists with Dec2013 release. After wasting an entire day, I used your DLL and that finally resolved the issue.

FrElIT wrote Jan 17, 2014 at 1:05 PM

For me it seems to work when I use IE9 running in IE8 mode but not working when I use IE8.
Probably some settings that is wrong but I cannot realise which setting.

Kartris wrote Jan 17, 2014 at 2:44 PM

FrEIIT, there are two issues which can affect how a browser renders things when connecting to a .NET site. One is the rendering engine of the browser (i.e. what the browser does with the code it receives from the server). The other is the User Agent, which affects what HTML actually sends to the browser. So if testing with the F12 dev tools in IE, make sure you set the Document Mode and User Agent String both to IE8.

elraperoculero wrote Feb 5, 2014 at 7:51 PM

This dll update really save my day!!!!... I just want to say thanks!

schlubadub wrote Apr 14, 2014 at 7:36 AM

A similar issue exists in it would be great if someone could provide a fixed DLL for that version

chrislynn5 wrote Apr 22, 2014 at 3:22 PM

Any updates? I realize IE8 is oold but many users are still on it. Not to mention that this works in the older 3.5 ToolKit. That's hard to explain to existing users. Thanx.

chrislynn5 wrote Apr 22, 2014 at 5:52 PM

The source section for the AjaxToolKit shows 2013's version with a fix (referring to this topic)???
Why is this topic closd when the issue carried over to the latest 4.5 version

That latest source explains how the tab control was rewritten in jQuery. But it broke existing functionality. My web app worked prior to upgrading the toolkit. And latest toolkit is broken.

This should not be closed. Thank you.

euristika wrote May 17, 2014 at 10:25 PM

They closed, but fix was not provided, So, anyone knows where how we can fix this problem?