Summary of css debugging methods

This summary is constantly updated. It mainly records the experience and methods terminated during debugging.

After all, I am not working as a browser front-end, so if you have any questions, please forgive me.

Css is related to the appearance of the interface, and sometimes functions are implemented. The interface is really ugly, but it is still a failed product. All good products require not only practical functions, but also beautiful appearance.

1. If the overall layout is adjusted, the layout will be offset.

You can use the browser to retrieve the path offset component (magnifiers) and then modify the css effect applied to the css file of the component, as shown in:

You can get the css style and css details on the right side: <Strong? Http: www.bkjia.com kf ware vc "target =" _ blank "class =" keylink "> VcD4KPHA + sum/tLW90fnKvbrzo6y7ub/J0tS/tLW9ttTTptH5yr3L + logs/ttzvfjq0nh5yr3q31_evls/fingerprint = "http://www.2cto.com/uploadfile/Collfiles/20140614/20140614091507194.png" alt = "\">

And css details:

Component size: 177 + 10 + 10, height: 18 + 8 + 8

Widget padding: 10

Component boundary: the boundary of the component indicates that the component is not an integral part of the component.

As shown in the left figure above:

There can also be an outer boundary outside the boundary: margin: indicating the length and width of the component.