Front-end coding habits - html article

Preface

As a front-end engineer, we may have to write html, css, and javascript every day. The code written by everyone contains their own personal style and has their own coding habits and guidelines. The following is Let me share with you my habits and rules.

html

First of all, we need to standardize the document, so we need to addto standardize the document. There are corresponding instructions aboutw3c.

The encoding adopts utf-8 uniformly, that is.

When citing css style or js in the page, there is no need to add a type declaration. For example:

Omit the protocol portion (http:, https:) of the URL of images, styles, scripts, and other media files, unless the file is not available under both protocols. This scheme is called protocol-relative URL, relative protocol URL. The advantage is that whether you access the page using HTTPS or HTTP, the browser will request the resources in the page using the same protocol, while saving some bytes. When the browser encounters a relative URL, it will automatically add the same protocol in front of // according to the current web page protocol. If the current web page is accessed via http, all relative references // will become http://. Same goes for https. If you view it locally, the protocol becomes file://. This usage is supported by almost all browsers. There is only a small problem under IE7/8, that is, CSS files referenced through relative URLs (regardless ofor @import ) will be downloaded twice. So it has a little impact on performance.

    /* Not recommended */ .example { background: url("https://www.google.com/images/example"); } /* Recommended */ .example { background: url("//www.google.com/images/example"); }

Tags, attributes, and attribute names are all lowercase, and attribute values are enclosed in "" (double quotes). Each double tag must be added with the corresponding end tag (single tags do not follow this standard, and still use the original html standard, that is, it does not need to end with "/>"). Reminder: Many page deformations under IE are related to unclosed tags or nested errors.

Tags should be nested reasonably in order. For example:

 需修改为：