IE8 is a nice browser, it renders the Acid 2 test perfectly and Microsoft has finally taken a leap of faith that not even Firefox has.
But with a leap of faith comes a host of issues, IE8 will not render a whole lot of sites very well. Including Blogger. I couldn't post this from IE8.
And all the CF8 Ajax / DHTML features are broken. Even in IE7 emulation mode the grids will not render correctly.
So who's fault is this? Is it Microsoft for being so brave, Adobe for including DHTML stuff, EXT for not working.
Well it's a combo, but most notably Adobe will have to fix it, and hopefully fix it by moving to EXT 2 rather than anything else. Others have blogged that ColdFusion including large libraries of javascript and DHTML was risky, Adobe are aware of this and now have no choice but to fix it.
Now Adobe need to release a CF8 update before Microsoft release IE8.
4 comments:
we really have pushed the browser a loooog way... too far for my liking (hence seeing a SWF world making more sense to me)
I'd love to see how IE8 works with ASP.NET... esp the Atlas (Ajax) stuff...
Dale,
See my blog on IE8 for Engine switches. As for styles, there are bugs in the rendering at the moment.
But I guess you know this because it is Beta.... Right.
if you use my blog, and switch the meta tag to only contain IE=7 everything works perfectly.
Or you could leave it in emaulate IE7 permantley:-)
IE8 even broke the entire home page of www.adobe.com :)
What would be nice is to see Adobe release updates to the CFIDE/scripts folder which would include upgrading to EXT 2, and possible a newer version of FCK Editor.
Post a Comment