1. Once, online falsification styles have bothered you?

Useful_tips_for_Chrome_Developer_Tools_1.jpeg

2, the source code is quickly positioned to a certain line! Ctrl + p

Useful_tips_for_Chrome_Developer_Tools_2.gif

3, when the joint interface fails, the background boss always wants you to respond?

Useful_tips_for_Chrome_Developer_Tools_3.gif

4. Do you still expand dom layer by layer? Alt + Click

Useful_tips_for_Chrome_Developer_Tools_4.gif

5. Is it an error, are you going to break the point?

Useful_tips_for_Chrome_Developer_Tools_5.gif

6. Do you often miss it, where do you bind events?

Useful_tips_for_Chrome_Developer_Tools_6.gif

7. Do you still need to change the code when you break the point?

Useful_tips_for_Chrome_Developer_Tools_7.gif

8, the most intuitive way to see the dom level?

Useful_tips_for_Chrome_Developer_Tools_8.gif

9. Check some specific requests. Has the filter been used?

Useful_tips_for_Chrome_Developer_Tools_9.gif

10. Is it inconvenient to adjust the dom structure in the Elements panel?

Useful_tips_for_Chrome_Developer_Tools_10.gif

11, I want to know, where is the code loaded by an image? Initiator! !

Useful_tips_for_Chrome_Developer_Tools_11.jpeg
Useful_tips_for_Chrome_Developer_Tools_12.jpeg
Useful_tips_for_Chrome_Developer_Tools_13.jpeg

12. Don’t want to load a file?

Useful_tips_for_Chrome_Developer_Tools_14.jpeg
Useful_tips_for_Chrome_Developer_Tools_15.jpeg