There are more and more browsers supporting CSS3 and HTML5, even including the latest version of IE. Of course, the so-called support is only partial support, because the W3C specifications for CSS3 and HTML5 have not yet been formed. If you want to create your site with CSS3 and HTML5 now, at least have a comprehensive understanding of the support of each browser for these two new technologies.
It should be noted that even in the same version of the same browser, their support for CSS3 and HTML5 is not consistent on both Mac and Windows platforms. This article is a detailed list of Chrome, Safari, Firefox, Opera, IE 5 major browsers, and Mac and Windows platforms, for various CSS3 and HTML5 functions.
It can be seen that browsers that fully support CSS3 attributes include Chrome and Safari, and both Mac and Windows platforms are fully supported.
Except for the IE family and Firefox 3, almost all others are supported. Chrome, Safari, Firefox 3.6, Opera 10.5 has the best results.
Safari supports HTML5 web applications best, except for geolocation, everything else is supported.
This should be the most anticipated thing in HTML5, built-in canvas, video, audio and other objects. All supported are Chrome, Safari, Firefox 3.6, and Opera 10.5. The IE family was wiped out.
Opera 10.5 supports the most comprehensive, and the IE family is inseparable.
H.264 There is a long way to go.
Chrome is the best on the Mac platform. These form objects are reminiscent of desktop programs.
I thought of desktop programs again.
Currently, Safari is the best support for CSS3 and HTML5, followed by Chrome, Firefox 3.6 and Opera 10.5 are comparable, and the IE family is the worst. In view of this situation, if you want to use these two new technologies to create a pioneer experiential site, CSS3 and HTML5 can be implemented now. If you want this site to be accessed normally by most people, it is too early to now. The compromise solution is to provide a downgrade solution for browsers that do not support certain functions of CSS3 and HTML5. Of course, there are many issues involved, including browser, version, platform detection, CSS Hack and other large amounts of work, which is believed to be not worth the effort.