This article analyzes in detail the reasons why IE9 does not support some attributes in HTML5, and shares it with everyone for your reference. The specific method is as follows:
As we all know, IE9 does not provide support for offline applications in the HTML5 standard and some parts of CSS3. This article makes a brief analysis of this.
Microsoft has recently released the official version of Internet Explorer 9 (hereinafter referred to as IE9). In this version, Microsoft follows their development strategy and provides support for most features in HTML5 and CSS3, which are the latest web standards.
At the same time, Microsoft is also preparing to use IE9 applications in Windows Phone 7. IE9 has undoubtedly become a very important link in Microsoft's Internet strategy.
However, in the now released IE9, several major features in HTML5 that should be used to compete with browsers such as Firefox, Safari, and Chrome are not supported.
The HTML5 announced by W3C and the main functions related to it are listed as follows:
Communication related (Web Sockets, Server-Sent Events, etc.)
CSS3 style
Device positioning function (obtaining geographical location information, etc.)
3D and screen display effects (3D function of WebGL, CSS3 etc.)
Multimedia (Audio/Video, etc.)
Performance and functionality improvements (Web Workers, XHR2, etc.)
Semantics (Microdata microdata, etc.)
Offline and local storage (App Cache, Local Storage, IndexedDB, etc.)
Among them, you can use web pages even offline, the functions of web applications, multi-threaded Web Workers using JavaScript, and several in CSS3 None of the features are supported in IE9.
Why doesn’t Microsoft, which should actively support HTML5, provide support for these important features in IE9? In this case, why is it necessary to use IE9 in Windows Phone7? This reason was answered by Microsoft officials.
Question: First of all, confirm the fact that IE9 does not provide support for HTML5 offline functions, etc.?
Official answer: Indeed, generally speaking, the offline function and several functions in CSS3 are not supported in IE9.
First of all, let’s make a note about CSS3. The vendor prefix in CSS properties ("-moz-", "-webkit-" added before CSS properties in order to be used in browsers provided by other vendors) etc. prefix. ) is not supported in IE9.
In IE9, "unified tags" are advocated, which means that the same attributes and tags should have the same rendering effect in any browser. In other words, various prefixes artificially added for use in browsers provided by various vendors do not conform to this concept, so support is not provided.
There is another question about offline applications. This is because the implementation method of one of its related functions, IndexedDB, has not yet been determined, so the offline application functions closely related to it are not supported yet.
Currently, IE is used by various customers including individuals, developers, enterprises, etc. Therefore, a conservative approach must be adopted for the support provided for new functions.
The support we provide now is very safe and stable, and in the future we will give priority to supporting those features that have a very high level of desire among users.
If all functions are supported at once, or if certain functions are specifically supported to cater to enterprise users, this kind of support is very unsafe and unstable, so we do not want to take this approach.
However, the enhancement of IE functions will definitely not stop at IE9, so we will definitely continue to provide new support for HTML5/CSS3 in the future.
Question: In fact, in IE9, the offline function and WebWorker function, one of the main functions of HTML5, are not supported. This is a matter that has attracted public attention recently. While claiming to provide support for HTML5, without clearly stating what functions are supported and what functions are not supported, doesn’t this kind of publicity mean there is no such thing?
Official answer: It’s not that I wanted to hide it. I was probably busy giving a comprehensive introduction to a new browser like IE9 and didn’t take this issue into consideration. Of course, when each API attribute is introduced separately, there must be a relatively clear explanation.
I hope this article will be helpful to everyone’s HTML5 programming design.