If there is no IE6, how will the div css road go?_html/css_WEB-ITnose

If there is no IE6, how will the path of div css go?

Once upon a time, front-end developers and front-end reconstructors were all suffering from the BUG of IE6. The most classic one did not support PNG transparency, etc., and there were many, many puzzling problems. I guess Many friends like me who are engaged in front-end development are aware of the various bugs of IE6. So, front-end developers, have you ever thought about what changes would be seen in the div css path without IE6? In other words, without IE6, how will your work change? Let's not mention these first, let's take a look, what changes will happen to web page reconstruction if there is no IE6?

1, support PNG images
There is no need to design different image edge anti-aliasing solutions under different background solutions as before, and struggle to find IE6 png transparent solutions, so that hateful The translucent webpage of IE6 looks personalized, and the floating layers such as lace and lace are also perfectly displayed.

2. There is no need to set the floating double margin of margin for the display

You can use code similar to display:inline-block, so that insets will no longer appear. There is no need to hesitate to use definitions such as overflow:hidden to avoid the confusion of float:left.

3, min-width and max-width can also be used perfectly
Although IE6's implementation of width is very close to the correct min-width, it is always different. And there is no max-width involved. With the disappearance of IE6, a new block-based layout method will be revived, which will be more flexible.

　

4, which can reduce the number of css hacks by 90%
There is no need to set the floating double margin problem of margin for display, and there is no need to write special Hacks for these bugs. You can boldly believe in z-index, and you don’t have to scratch your head about the wrong stacking order between layers. We didn’t do anything wrong. This is caused by the IE6 stacking BUG.

　

5, save time
Those png transparent layers and inexplicable css hack problems will waste a lot of our time and make front-end reconstructors work on these The tangle of bugs in IE6 is not the fault of the reconstructor, nor the fault of IE6. I guess these questions should be asked to the developers of Microsoft IE.

6. Damn IE6, what are the bugs in IE6? Let’s take a look at this article.

JavaScript, improve JavaScript execution efficiency and performance. We still have a lot of room for improvement in JavaScript, a simple event listening mechanism, etc., providing JavaScript performance is also a big change. If there is no IE6, how will the div css road go?