The code of the seventh PPT uses JS to set CSS. This has nothing to do with "different browsers parse DOM differently", it is the compatibility of CSS! Moreover, using JS to directly set styles is a technical mistake!
The code of the ninth PPT is programmed with DOM script, instead of using the more compatible form name to retrieve the objects in the form. It seems that DOM scripting cannot live without the XXX.getElementByXXX method.
The code for the 10th PPT is:
if(document.all){}else{}
And the code is obviously the addEventListener() method, so why not write it like this:
if(XXX.addEventListener){}else{}
For the reason, please see army’s translation "Feature detection is not browser detection".
Well, document.all(IE) and document.layer(NN) are quite ancient writing methods. I have only seen some traces in the code left behind by the project. It is really a headache to use it in large quantities like Adang. See you later.
The code of the 19th PPT uses a JS closure formed by an anonymous function to generate a temporary namespace. Through communication with colleagues, I found that this method can only be used once in the core file of the library ( See jQuery source code). If it is used more than once in a page like this, it may be misused. Judging from his code, a already has the difference between A and B, so there will be no conflict.
In the code of the 25th PPT, the set method and read method are not paired, set and get are paired, and read and write are paired.
ppt package download