Parse the difference between CSS + DIV in IE6 and IE7

This article briefly describes the differences between CSS + DIV in IE6 and IE7. The width of IE7 is wider than that in IE6. This is the reason why the webpage may have overflow problems, fortunately, you can change the value or change the percentage.

Difference between CSS + DIV in IE6 and IE7

1. IE7, IE6div + css have different width Definitions

In terms of width definition, the width of IE7 is wider than that of IE6. This is the reason why the webpage may have overflow problems, fortunately, you can change the value or change the percentage.

2. IE7.0 is fixed! Important bug

Previously due to IE6.0 pair! Important identifies bugs. The BOX model interpretation in firefox and IE is inconsistent, resulting in a 2px difference. Most Web Standard designers use this bug to be compatible with IE6.0 and firefox, that is, using: div {margin: 30px! Important; margin: 28px ;}. However, IE7.0 fixed this bug, so the problem emerged again. How can I be compatible with IE.7.0 and IE6.0 and firefox?

3. Change of BoxModel

In IE7, overflow behavior is modified to adapt to CSS2.1boxmodel.

4. Some CSS filters in IE7.0 will no longer be available

Many potential resolution errors have been modified in IE7, which may prevent filters from working properly in earlier IE versions. For example, * HTMLfilter, underline filter, And/*/comment filter.

5. IE7.0 does not support many nonstandard css statements and has stricter requirements on js syntax.

Many js pages normally displayed in IE6 cannot be displayed normally in IE7, and no error is prompted. IE7.0 has stricter requirements on js syntax, but this specification does not seem to be explained, and it does not clearly tell you how they are "standardized" and "Fan.
Browser incompatibility has always been a headache for web designers. Whether or not IE7.0 is better than IE6.0, IE7 and IE6 are incompatible. There is no doubt that new pain points are introduced, at least in the debugging process, there is another program and a large number of incompatibility problems.
At present, there are still a few users using IE7.0, and IE6.0 still accounts for a large proportion of users. However, a large number of web pages tested by IE6 are not displayed properly in IE7.0.

According to IE7.0 official comments:

IE7.0 introduced the strict mode based on IE6, including many improvements on parsing and rendering of Cascading Style Sheets CSS. These improvements are intended to improve InternetExplorer's interpretation of the consistency of Cascading Style Sheets to meet W3C recommendation standards and provide developers with a set of functionality that can be relied.

No matter how beautiful the official language is, or whether IE7.0 is really W3C, there are too many personalized things and too many differences between browsers, which makes us helpless. The web page displayed under IE6 is almost unsightly under IE7.0. So when we design the web page, while solving the compatibility problem between IE6.0 and Firefox, are we more obedient to IE7.0 that comply with W3C or compromise with IE6.0 of 96%? This problem is actually a bit redundant. What we can do is perhaps the moderate choice. We only need to try to debug it to all browsers.

The compatibility and alternation of old and new technologies are very important. Early exposure and absorption of new technologies are a good thing. However, compatibility with old technologies is even more important, because most customers are still using old technologies