AJAX and IE7?

Moochfish asks: "Recently, my company took a brief look at AJAX to see if it was worth implementing on a few of our administrative pages to speed up certain tasks. I had created a demo that made an interesting use of live edit fields that showed some promise. However, after a little debate on the issue, we ultimately decided to skip AJAX implementations anywhere in our codebase due to concerns about things breaking when IE7 comes out. I haven't personally tried IE7, but I completely understand and mirror the concern. For you testers of IE7, does it successfully render current, non-ASP AJAX enabled sites without errors? And finally, does IE7 introduce any new functionality that may enhance the current capabilities of AJAX?" "Many of the AJAX libraries out there have tons of duplicate functionality to handle cross-browser support. Recalling Microsoft's history of IE quirks, it seems likely that the new IE7 will have its own set of problems with regards to JS implementation. With the AJAX craze only growing, how are other developers and IT departments addressing this problem? Is this even a valid concern? While this is probably not an issue with ASP developers - especially with the release of Atlas - is this an issue for sites that use non-MS technologies?"

Comments

easy solution

[chef_raekwon]

just have a popup on your page that automatically downloads, installs, and launches firefox.

When will people learn...

[Baloo Ursidae]

...that people will not stop using IE until you stop supporting it? Fuck IE, code for the standard, if it breaks IE, tough crap, they can get another browser.

dumb

[namekuseijin]

"does IE7 introduce any new functionality that may enhance the current capabilities of AJAX?"

yes, it'll come with the almighty proprietary XAML technology M$ stole from Mozilla XUL. and everyone will bow to it and an html web will be gone...

You're really serious about waiting for something which you even fear might break your efforts? Talk about reasonable businessman...

There should be no wait or fear if you just coded for standards so that it would run on any browser. Or just go for Firefox, which is here now and works great, with great standards-compatibility which won't simply disappear in some future version.

If you're believing IE7 will be any close to Firefox in either standards compatibility or sheer top-notch features, you'll be severely letdown, as with most M$ products: it's nothing but a patched IE6 with some more much-needed uptodate css support, something FF has had for several years by now...