Introduction to w3c standards

# W3c standards # What are w3c standards? w3c standards include multiple aspects, which are officially divided from the application perspective. Relevant documents can be stamped [here] ( http://www.w3.org/standards/ ). From the perspective of WEB technology, there are three standards: ** structure, performance, and behavior **. Structure mainly refers to the (X) HTML standard, including the names, attributes, semantics, and other related standards of various tags. The performance mainly refers to CSS, including various positioning, color, size and other standards. The behavior mainly refers to Javascript, which is mainly developed by ECMA international standards. However, because it is widely used on the World Wide Web, developers should also pay attention to it. Javascript also has a series of standards in terms of lexical, expression, and statement. Javascript is not a ready-to-use binary file like Java JDK, but only provides document standards. The specific implementation is handed over to various browsers. Therefore, the compatibility of various browsers is a problem during development, we can follow the duck-style pattern recognition principle for processing. # If the standards are not met, it is critical to unify the standards to improve development efficiency, especially for team development. If the teammates who develop together do not comply with the standards, I use lower-case tags, and you use upper-case tags. elements are not closed at will, and attributes are not caused by double quotation marks. [DocType can be randomly placed] ( http://www.cnblogs.com/p2227/p/3556652.html ), So we may have unnecessary errors or logic problems. It is a waste of time to troubleshoot these problems, and these times can be avoided at the beginning. Okay, you can only work overtime to make up the time. Different standard pages give users the feeling that your product is not professional and your score will be compromised. Just like the naughty IE, we always don't listen to the standard, and everyone uses addEventListener. You use attachEvent, which has received the BS of countless developers. Well, I know that IE has appeared earlier than w3c standards, and IE9 has started to turn its back to evil. The emergence of IE11 is especially surprising. Wait and see. # Following the standards, how can we disappear? HTML5, a standard. After the birth, the WEB industry became an uproar and the browser became a panacea. Many UI libraries, even silverlight and Flash, are useless. How MS, adobe, and w3c NB. All major industry websites use this dynamic news as the highlights of the headlines. Many recruitment information like to add a ** HTML5 priority **. Standard, great influence. Level-1 enterprises adopt standards, level-2 enterprises adopt brands, and level-3 enterprises sell goods together. To improve the level, the standard is critical. Specifically, web development is a w3c standard. # How to Implement w3c standards first requires that all the Members in the team be familiar with it, and some common ones cannot be violated. Next, we should pay attention to it frequently because the standards are not fixed. For example, now HTML5 script elements do not add type, and new standards have new writing methods. Again, we work out applicable w3c standards based on our own teams. After all, we need to remember what we often use. Otherwise, our programs do not need to write comments. # What are the details? How can we deal with the unruly rules of new members? New personnel training is still very important. Formal companies should have these specifications. Did the previously completed products not comply with the current standards? Gradually improve the product in the next standard based on the product operation cycle. Does my work conform to the standard? Click [here] ( http://validator.w3.org/ ) Check it out. # Reference http://blog.163.com/big_shrimp/blog/static/7282689320102212623417/http://www.w3.org/