Let domestic dual-core browsers use the chrome kernel to parse.
In fact, there are really not many users in China who use IE6 and IE8. The vast majority of XP users use domestic dual-core such as 360.
In addition 360 has its own tag
<meta name="renderer" content="webkit">
Can force the use of Webkit kernel rendering.
See: http://se.360.cn/v6/help/meta.html
If you really want to use the effect in lower version browsers, there seems to be such a JS library, you can look for it.
Go and give me something that will only be available in the future and try it! ! !
The advancement of computer technology, in addition to extensions that do not destroy the old implementation, is inevitably accompanied by drastic deprecations and fixes. In fact, I think the questioner just accidentally ignored these two possibilities, rather than there really being an IQ problem that hinders understanding of technological progress.
The above statement is too absolute. It depends on whether the developer considers compatibility with lower version browsers during development and what functions are implemented.
First of all, we need to understand what functions html5 implements.
Local storage function
canvas
files api
video,audio
. . .
These functions are not supported by HTML in lower versions. If this function is used, it will definitely not run.
The original poster said that the style is confusing, the reason should be
A large number of new HTML tags are used, which are not recognized by IE7 and below and cannot be parsed. The general solution is to createElement a tag with the same name.
It should use more CSS3 styles, which cannot be used in old browsers. For example, the layout method is very different.
. . .
So, if the author wants to see whether it can be viewed normally in other browsers, please consult your front-end technical staff.
If you want to be compatible with lower versions, don't use html5. Compatibility is difficult to guarantee. Please confirm compatibility before writing it in
html5 is a standard. Do we need standards to accommodate outdated things? Standards mean that others must abide by them. It can only be said that lower version browsers cannot support new standards. Technology is advancing and metabolism is inevitable!
I think the title should be called
Why are older browsers not compatible with new technologies! ! !
BetterWhen I create a page, I just use the low-version browser hack to ensure that the page layout is not messy and add tags
Let domestic dual-core browsers use the chrome kernel to parse.
In fact, there are really not many users in China who use IE6 and IE8. The vast majority of XP users use domestic dual-core such as 360.
In addition 360 has its own tag
Can force the use of Webkit kernel rendering.
See: http://se.360.cn/v6/help/meta.html
If you really want to use the effect in lower version browsers, there seems to be such a JS library, you can look for it.
Go and give me something that will only be available in the future and try it! ! !
The advancement of computer technology, in addition to extensions that do not destroy the old implementation, is inevitably accompanied by drastic deprecations and fixes. In fact, I think the questioner just accidentally ignored these two possibilities, rather than there really being an IQ problem that hinders understanding of technological progress.
html5 products cannot run on lower versions
. . .
These functions are not supported by HTML in lower versions. If this function is used, it will definitely not run.
. . .
So, if the author wants to see whether it can be viewed normally in other browsers, please consult your front-end technical staff.
If you want to be compatible with lower versions, don't use html5. Compatibility is difficult to guarantee. Please confirm compatibility before writing it in
Add the following sentence in the
head
taghtml5
is a standard. Do we need standards to accommodate outdated things? Standards mean that others must abide by them. It can only be said that lower version browsers cannot support new standards. Technology is advancing and metabolism is inevitable!How do you make it compatible with something that doesn't exist?
When IE6 7 came out, html5 was not yet a standard, so why should we be compatible with a non-standard thing
I want to ask, are you a technician?
Everyone has said it before.
In order to make lower version browsers (don’t look, I’m talking about you IE!) compatible with html5 tags, add
html5shiv.js
.