Basic ideas for finding errors in Web front-end development

WEB development mainly consists of two interactions (B/S data)

Browser:

1Contains errors in the execution of client codes such as html, css, and js.

Transmission side:

1. Path introduction errors, the introduction of common plug-ins (artDialog, Ztree, JQuery, etc.), image paths, video paths, etc.

2 The files (js, css, pictures, videos, etc.) are too large, causing the browser to parse slowly and the loading time to be too long. These files can be compressed appropriately.

Server:

1 Dynamic web page - data source (i.e. data operation program) error.

2 Data error in the database or file.

Simple diagram:

Common methods for handling errors on the client side (common tool F12):

1. For html and css debugging, just click the arrow (you can view the element attributes). For js debugging, generally set breakpoints.

2. Cache accumulation causes errors, clear the cache.

3. Page value transmission and request processing can capture requests and responses between pages in the network.

4. Cookie and Session processing and clearing.

Notice:

[Browser engine rendering method (taking IE as an example):

1. Browser browsing mode, that is, the default browser engine type {IE7 6 version is IE7 6 engine}

2. Document browsing mode, which is the actual parsing mode of the code

{You can set it manually with code: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> Regardless of the version of IE, the html code will be parsed by the IE7 engine}

The above is my experience in finding errors in WEB front-end design. My knowledge is limited, so please feel free to give me your advice if there are any loopholes.