IE7 provides XMLHttpRequest objects for compatibility _javascript techniques

In the development of IE7, it is said that a new native object--xmlhttprequest is added. How can the development of IE7 's "new police" not know IE6 are using ActiveX object XMLHTTP? XMLHTTP What's the problem, IE7 why do this? Originally all for a simple compatibility just, but let people feeling a lot.

IE7 provides XMLHttpRequest objects, of course, will continue to support ActiveX object XMLHTTP, this is Microsoft so many decades of product upgrades at least "literacy", the slightest need to worry about the current IE Ajax application code. In Sunava Dutta blog, although he said why to do so the original intention, in fact, is to be compatible with the current non-IE browser to provide XMLHttpRequest to use the situation of XMLHTTP. His "crappy" sample code was picked up by some burner comrades, but I felt that Microsoft showed his real interest in these "minutiae" issues.

This is going back to the years of IE and Netscape, when the heyday of Netscape is the absolute No.1 browser market, Microsoft because of the first time in the Internet strategy for Comrade Bill to take a nap, so that Netscape tasted a little tiger in the mountains, monkeys called Overlord feeling. When Bill issued: "I found that there is no Microsoft file format on the Internet is very dangerous," after introspection, Microsoft began to march on the Internet. One thorny issue, of course, is the strangulation of Netscape, then Netscape vs. ie, today's IE vs. Firefox. The former IE has Windows as its bundle of Green Express, the latter has today, we hold high security, the banner of the big banner of the Voice of solidarity, can be said to be formidable opponents but the newcomers are not good Lord.

In this war of strangulation, Microsoft is more stable to live in the air. Because IE 1.0, 2.0 or 3.0 (as if NT4.0 with IE3.0) are completely not Netscape's opponents, like the original VC + + and Bcc between the same rivalry, Microsoft is depressed. But Microsoft knew that it was not against Netscape, so the implementation of IE did a lot of compatible with Netscape's design, because then Netscape is not soft, the one hand created JavaScript, it is in fact the industry's default standards. The situation continued until Ie4.0,ie gradually took advantage (the bundle of Free + Green Express was not vegetarian) and Netscape's downfall was inevitable, when Microsoft began to aggressively design its own DOM, modify HTML parsing and render effects, Add a new HTML tag (this is Netscape's job), and of course the support for CSS is what Microsoft wants.

Today's IE7 support for the XMLHttpRequest object and Firefox dead embrace the so-called "standards of the International standard" form a clear contrast. Some days ago, someone in the classic scripting forum called on Web developers to boycott Firefox, although the word extreme and give the feeling is gladiators arm block, but some of his views I agree. is to hope Firefox and other non-mainstream (in fact, not IE) browser, can be more compatible with IE, rather than let web developers to do everything possible to compatible with a variety of subtle browser. Because of the cost, because IE has been an indisputable winner, the implementation of the new browser to modify the benefits of a change everywhere, and let web developers to compatible with a variety of browsers, is simply the vast number of working people's intelligence, labor insults.

Of course, many people may say that the standard is the eldest, no matter what browsers should follow the standards, otherwise are bull shit. But the reality of the situation is "store big pressure people, press shop", the other is meaningless. Like today, most of our web application technology is not standard and only RFC, we are not also happy to live well? Do not pull away to avoid becoming a crusade against the standard, continue to say the problem of the browser. For Firefox This "later" so long baby brother browser, no matter how perfect it to support the standard, I put my hands in favor. But in some of the cost of easy, why not good compatible with the following currently the most popular IE? For example, to use different DOM attribute name, must and IE draw a clear, you ie exclusive what runtimestyle, currentstyle, etc. sorry I just do not support, event is to get and you are not the same, anyway how awkward how to come. The final effect is to do most of the normal Internet Explorer page, the first time in Firefox run all the rest of the food, is this the next everyone is satisfied?!

If Firefox and other non-IE kernel browsers can care compatibility issues like Microsoft, their markets should be bigger and more promising. Firefox can fully provide two modes to run, one is the standard mode completely follow the Internet, one is IE compatible mode as far as possible compatible with IE. At this time the user can seamless transition, free choice, which its fast, security features can truly become an overwhelming advantage. And in its different popularity period to choose different operating mode as the default mode, can be a good solution to the standard promotion, and "wooing" other IE users of the contradictions between, but not for it?