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

Re:Firefox

[Anonymous Coward]

I'm sorry but that's an ignorant and frankly a fucking retarded answer. I prefer FireFox myself, but to tell a developer that he can solve his problems by telling all his users to switch to another browser... well that's just stupid.
Can you imagine going to a service center for your car, and their solution to your automotive problems is to tell you that they don't service your kind of car, so they've gone ahead and sold you a new one?

Great, FireFox rocks, IE has problems. That doesn't change the fact that we have to meet our customers needs, not the other way around.