1. js script cache Problems
A: This is one of the most common problems you have encountered, because when you modify the js content for debugging
The result of the newly written code cannot be displayed because the current page uses cache persistence to accelerate page execution.
The same connection currently called. To facilitate debugging during development, you can add a random function after the connection address.
For example, the original address: Add random header. js in header. js? 12581
2. Local debugging of js scripts does not work
A: Because head support is required when parameters are passed Using ajax, we can only use it under the site.
Successful. For example, we put it under Apache or IIS for debugging.
3. Difficult to troubleshoot code
A: This is a long-standing issue in js debugging. to simplify it, you can use the default error box prompted by ie.
Yes. We can use the error correction provided by DW CS4, or use professional plug-ins such as firbug.