The top empty element. You can also use the style selector to add inline styles to overwrite everything else. I often use this view to understand why my style rules don’t work, the selectors used to specify elements as targets, and the elements displayed by the modified CSS. The element on the right. There are two icons next to the style section. Use the plus icon to add new style rules, selectors, and so on. Another icon opens a new section where you can view activity, focus, Hoover, and access status. You can view its status and create specific rules for it. The
The JavaScript task developer tool provides very powerful functionality for JavaScript, which is somewhat similar to the ide in this regard. JavaScript is easy to build because it is a client, so chrome can access all the required content. The console console is the starting point for most JavaScript debugging requirements. You can provide any type of information in addition to JavaScript. In the screenshot on the chrome developer tool console, you can see some good suggestions (blue) and two problems (red). The message is displayed with the source file to find the location of the problem. The
If you connect and collapse JavaScript, don’t forget to create source mappings. In this way, you can see the actual problem in a large amount of code, rather than the description. Alternatively, you can wait for the script to shrink until the product is pushed into production. Click the arrow to the left of the message for more information about the problem. If you click the 404 wrong arrow, the problem is actually global. Although JS is available, jQuery. JS bubble jQuery. JQuery of JS. There are JS. Clicking on a file actually moves to that file. Great! The
When debugging scripts, our scripts sometimes fail to work for unknown reasons. Script debugging can help you identify problems and easily resolve them. Breakpoints are often used. The concept is very simple, but the tools provide too many functions, so it is difficult to find the way. Breakpoints are essentially intentional stop signals generated to interrupt the operation of code. Use various controls to check the operation in progress (used variable values, etc.) on the breakpoint. You can continue to run when you are ready. The first stop must be the source panel. You can use command+p (control+p for Windows users) to open the file. This opens the script on the left, and you can control the flow using the tools on the right. The
Click the line number on the left to set the breakpoint. They are displayed in the breakpoints section on the right. You can then rerun the script that stopped at the specified location. Add JavaScript breakpoints conditional breakpoints, and use this part for all types of other debugging magic. It is recommended that you read the Google Chrome documentation to debug JavaScript. Very useful! Network part the network part provides rich data for requested and loaded assets. Display request status, type, size, loading time, loading timeline, etc. You can learn a lot here. I use it for:
Error request troubleshooting load time bottleneck finding Ajax request data confirmation developer tools network part error request items show the request method, status and type. Methods and types rarely need to be modified, but state is important. Of course, note the 404 error shown in red. Click the status heading to sort the list by status. Click 404 again
Get lost immediately. Understanding this tool is a great asset for development and is worth the time to learn. In addition to the functions I have covered, there are more functions. Please look around. If you think you need more, please visit the extension library to find chrome extensions that add more content. If you use other browsers (such as safari or Firefox), you also have your own developer tools. Most functions are provided through different user interfaces. I like chrome or Firefox because I personally provide a large number of extensions. Do you use chrome developer tools? Please tell us the following comments. Tag: Browser password developer