ASP.NET Controls Now Support Internet Explorer 8 Standard Mode

16 July 2009
Neon IE Logo by Chris Wilson (IETeam)

A lot of us web developers don’t use Internet Explorer as our daily surfing web browser. But the fact that it’s still the most dominant browser means that we’ll be supporting it for quite a while.

In fact, the lastest version is pretty darn cool. Internet Explorer 8 with its performance improvements, accelerators, smarter address bar, and safety features is impressing a lot folks.

So, in the next DXperience 2009 volume 2 release, we’ve added:

Support for IE8 Standard Mode

All our ASP.NET controls are now correctly rendered for use with Internet Explorer 8 (standard mode).

Yup, all of them. And a special thanks goes to Microsoft for helping with ongoing issues which many of you have reported.

Have you and/or your organization upgraded to IE8?

30 comment(s)
Chris Walsh [DX-Squad]

Yes we have, SharePoint 2007 SP2 run's faster in IE8 so it was an easy decision...

16 July, 2009

"A lot of us web developers don’t use Internet Explorer as our daily surfing web browser."

And what is your sample size? 1? :)  And is this person (or person's) also yielding and iPhone? :)  MmmmHmmmm!  Busted!

Sorry, MOST of us are using IE 8 (My sample size: 1) :)

16 July, 2009
Mehul Harry (DevExpress)


Smile That's funny.

IE8 is good but Chrome (even Safari 4) seems to be the fastest right now and Firefox is great if you need the plugins.

Besides, with DevExpress ASP.NET controls supporting XHTML, you can use any of them. :-)

16 July, 2009
Christopher Todd

IE8 here! Never liked FF much until 3.5. Don't like Chrome and I really don't like Safari. I use the iPhone safari, but hate it! Very slow. I might try Chrome again in a few months. I work in State Government at one of the largest agencies and our standard is IE. We don't force it at gun point, but we develop for it and support it 100%. Everything else is at the user's own risk although I have begun to consider supporting FF. Using DX makes my job so much easier!

I would be interested in hearing what major issues where found with the current controls and IE8. I have only experienced one major issue with the GridView with IE; FF renders it correctly. B137783. The solution provided wasn't really feasible, but I just said the heck with it and moved on.

17 July, 2009
Richard Morris (DevExpress)

I use Firefox with to develop ASP.NET apps on (in a Windows VM on a Mac).  I haven't seen anything that comes close to it for Web dev.

But for daily browsing I also use Firefox because it supports swipe gestures under OSX and isn't Safari.

17 July, 2009
Bojan Vrhovnik

Well, i do prefer IE8 for alot of features (tab grouping, accelerators, address bar,...) and like it (also developer toolbar is jandy). I'm glad, that you're supporting IE8. In our company, the majority of users are IE8 powered :)

17 July, 2009
Peter Thorpe


Yeah firefox with firebug is my favourite by far, the info you can get about a page or element of a page is brilliant.

Couple that with trying in place adjustments of web pages. It saves me going back to visual studio every minute to try layout changes.

17 July, 2009
Robert Teague

I don't use anything BUT IE.

17 July, 2009
Christopher Todd

Okay, well I can admit when I am wrong! I decided to give Chrome one more try and I am happy to say that I am quite impressed with the performance. I wish it would allow pass-through authentication, but other than that it is nice. I wish the same for FF as well.

17 July, 2009
Mehul Harry (DevExpress)


Yes, agree, the Firefox plugin model and the community around it  is great.

17 July, 2009
Mehul Harry (DevExpress)


Yes, for many years I used IE exclusively as well. Smile

17 July, 2009
Mehul Harry (DevExpress)


Early versions of Chrome had issues. Since it came out of beta, it's been stable.

17 July, 2009
Mehul Harry (DevExpress)


Good point about the browser dev tools:

Firebug for Firefox

Fiddler for IE

Chrome's built-in dev tools

17 July, 2009
Juan Carlos Chávez Trinidad

I love Opera.

Opera has a very big support for all standars !!!!

19 July, 2009

I only use IE for browser compatibility testing

20 July, 2009

IE? it is crap... sorry to say that... I downloaded and installed to my computer.. when I first attempted to run it:) it crashed:))) it is weird..

20 July, 2009
Steve Sharkey

IE only for me - I use a lot of different computers and it is pretty much guaranteed to be on all of them. I'm afraid Chrome will never be installed on one of my machines - they put me off when they started releasing all their Google toolbars that seemed to be bundled with every piece of software that I installed for a period of time (always defaulting to ON). As much as Microsoft keep getting slated for their anti-competition practices, Google are effectively one big Marketing organisation (I've never taken to marketing people) who seem to want to out "Microsoft" Microsoft.

21 July, 2009
Aaron Smith

A lot of us use multiple browsers. Some prefer using FireFox mostly, others choose Chrome. I use FireFox, Chrome, IE 8, and Safari pretty evenly. I like the new dev tools in IE 8, but FireBug still has more features and Chrome's dev tools do things that IE 8 and FireBug do not do so well.

22 July, 2009
Andrew Badge

I use IE. Faster than Firefox and more features than Chrome.

29 July, 2009
Mehul Harry (DevExpress)


Opera is a nice browser but not enough market share like IE and FF.

29 July, 2009
Mehul Harry (DevExpress)

ObnoxiousBob, Mescut, Steve,

IE is king with FF fast taking a lot of its market share. Every web developer has to consider that IE is going to be a target when developing sites. What someone uses for day to day browsing is probably just a personal choice. Smile


29 July, 2009
Hal Roseman


Do you mean volume 1 won't  support IE 8 version?What about future release of IE 9,10 releases etc, each time new version of IE release you guys will ship with another new deve exp release ??can you please explain more detailly about this?

3 August, 2009
Mehul Harry (DevExpress)

Hi Robert,

Yes, IE8 support is in 2009v2 and going forward. Btw, all of our controls render XHTML 1.0 which means it can be rendered in any compliant browser.

IE8 has changed their internals on how they handle and render HTML. While improvements are great, it did tend to break some web pages. Take a look at the 'IE7' compatibility mode they introduced to help with the transition. I believe the IE team is working hard to resolve these issues. And we've had to make some adjustments to our controls to comply with the new IE8 standard mode.

As for the future, it's difficult to say how IE9 or IE10 will look or work. However, we will continue to support the top browsers.

3 August, 2009
Hal Roseman

Hi Mehul

Ok thanks.Do you guys have devexpres controls comparsion chart targetting differenet  IE Version?if you guys can provide that that helps a lot.

4 August, 2009
Mehul Harry (DevExpress)

Hi Robert,

While there isn't such a chart, I don't think its necessary. Our controls with the XHTML support will work just fine and if there are any issues, our support team is very fast in getting a solution out.

Hope that helps.

4 August, 2009

We're just about to release v2009.2 and it would be a good idea to have an "accumulator"

20 August, 2009
DotNetBurner -

DotNetBurner - burning hot .net content

12 September, 2009
Eugene Paradizov


you are stating that you are now supporting IE8 Standard mode, right? Yet, somehow, I find this doctype setting as the one DevExpress says to use:

DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" ""

As far as I know, this is not triggering the real standard mode (you can read about it here: The poroper doctype to trigger standard mode would be:

DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" ""


DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" ""

However, the controls are not working properly when either of these types are used. Any comment?

19 September, 2009
Mehul Harry (DevExpress)

Hi Eugene,

Spoke with our ASP.NET team and they have this to offer:

Yes, it's true when using our controls that you should use the

XHTML 1.0 Transitional document type. We chose this doctype because it provides the most flexible way for creating standards-based web sites. And our controls are specifically designed to work with this doctype. If you're using any other doctype then our controls may be displayed incorrectly.

Concerning the "real standard mode". There are two standard mode variants: standard mode and almost standard mode. I haven't found any mentioning in any official Microsoft source of how IE8 switches between these two modes, and how IE behavior differs. IE8 itself doesn't inform us which particular standard mode it's using for the moment. When using the XHTML 1.0 Transitional doctype, IE8 developer toolbar informs that IE8 Standards document mode is in use (screenshot).

Anyways, even if IE8 uses the almost standard mode instead of the "proper" standard mode, I believe, it's no big deal. For Gecko-based browsers, the almost standard mode differs from the proper standard mode very slightly. So, if IE8 works in the same way, it won't cause many problems for web developers.

25 September, 2009
Peter Jansson

I am very disappointed at IE8... Internet Explorer is still ages behind all the other browsers.

I can't think of any reason why anybody would want to use IE.

IE is slow, feature poor, and unsecure.

18 January, 2010

Please login or register to post comments.