This article mainly introduces the reason why IE9 does not support some attributes in HTML5. It is helpful for understanding the application of IE9 and HTML5. Friends who need it can refer to it.
This article analyzes the reasons why IE9 does not support some attributes in HTML5 in more detail, and shares them for your reference. The specific methods are as follows:
As we all know, there is no support in IE9 for offline applications in the HTML5 standard and for some in CSS3. This article provides a brief analysis of this.
Microsoft has recently released the official version of Internet Explorer 9 (hereinafter referred to as IE9). In this release, Microsoft followed their development strategy, providing support for most features in HTML5 and CSS3 as the latest web standards.
At the same time, Microsoft is also preparing to use IE9 in Windows Phone 7. IE9 has undoubtedly become a very important link in Microsoft's Internet strategy.
However, in IE9, several major features in HTML5 that should be used to compete with browsers such as Firefox, Safari, Chrome, etc., have not been supported.
Now list the HTML5 released by W3C and its related main functions as follows:
Communication related (Web Sockets, Server-Sent Events, etc.)
CSS3 style
Device positioning function (acquisition of geographical location information, etc.)
3D and screen display effects (WebGL, CSS3 3D functions, etc.)
Multimedia (Audio/Video, etc.)
Improvement of performance and functionality (Web Workers, XHR2, etc.)
Semanticity (Microdata microdata, etc.)
Offline and local storage (App Cache, local storage, IndexedDB, etc.)
Among them, web pages can be used even offline, web applications can be used, multi-threaded Web Workers can be used with JavaScript, and several features in CSS3 are not supported in IE9.
Why is Microsoft, which should provide active support for HTML5, not providing support for these important features in IE9? How to use IE9 in Windows Phone7? This reason was answered by Microsoft's official sources.
Question: First of all, confirm the fact that does not provide support for offline HTML5 functions, etc. in IE9?
Official answer: That's true. Generally speaking, the offline function and several functions in CSS3 are not supported in IE9.
First, let me explain it for CSS3. The vendor prefix in the CSS attribute (the prefix -moz-, -webkit-, etc. added before the CSS attributes for use in browsers provided by other vendors.) is not supported in IE9.
In IE9, unified tagging is advocated, that is, with the same attributes, the rendering effect of tags in any browser should be the same. That is to say, the various prefixes artificially added for use in browsers provided by various vendors do not conform to this concept and therefore do not provide support.
Another question is about offline applications. This is because the implementation method of IndexedDB, one of its related functions, has not been determined yet, so the offline application functions closely related to it are not supported for the time being.
Nowadays, there are individuals, developers, enterprises and other customers. Therefore, there must be a conservative approach to the support provided by new features in any case.
The support we provide is very safe and stable, and in the future, we will give priority to supporting functions that have a very high desire from users.
No matter what functions are all provided at once, or if certain functions are specially provided to cater to corporate users, this support is very unsafe and unstable, so we do not want to adopt this approach.
However, the enhancement of IE functions will definitely not stop on the IE9 version, so we will continue to provide new support for HTML5/CSS3 in the future.
Question: In fact, in IE9, offline functions and WebWorker functions, as one of the main functions of HTML5, have not provided support. This is a matter of recent concern to the public. While claiming to provide support for HTML5, I do not say clearly what functions are supported or what functions are not supported. Isn’t this publicity equivalent to not having it?
Official answer: It is not to conceal it specifically, but should be busy giving a more comprehensive introduction to the new browser such as IE9 without considering this issue. Of course, when introducing each API and attributes separately, there must be a clear explanation.
I hope this article will be helpful to everyone's HTML5 programming.