![reset inspect element chrome reset inspect element chrome](https://www.csestack.org/wp-content/uploads/2018/05/HTTP-header-in-Chrome-Inspect.png)
![reset inspect element chrome reset inspect element chrome](https://d33wubrfki0l68.cloudfront.net/4b140d6362edad687292423157422a6bf5d3b7c4/d8e26/assets/images/devtools-min.jpg)
Look in the Headers and see if everything looks normal. It will now show on the right your "Headers" and your "Response". If Ajax sent the request, it showed up in the Network tab.
![reset inspect element chrome reset inspect element chrome](https://itsmytrend.com/wp-content/uploads/2018/08/see-password-using-inspect-element.png)
Did a message show up in the Network panel? If no, it is not Perl's fault, it is something in your Javascript's ajax code. Leaving this open, interact with your web page so that your Ajax call would normally be made if it was working how you thought it should. In Chrome, open the debugging panel and click Network. No Javascript errors, but Ajax still doesn't work (also known as "Network help")
#RESET INSPECT ELEMENT CHROME CODE#
You can find everything in there, so if you think your code should have created a tag, try to find it! It may have appeared in a different place in your DOM than you expect, and this will help you discover that. This brings up the Elements and you can navigate your page's DOM tree. Right-click your page (anywhere), select "Inspect Elements". Use the "Elements" tab in the debugging console.No Javascript errors, but my DOM manipulation code still doesn't work Most likely this means printing a variable to see what its value is. You know what line the error occurs on, so put an alert("debug here") statement immediately before that line to print something useful. There is a Javascript error, but I don't know what it means If there is an error but you can't tell from the code what is wrong, see below. Are there errors in red? Look at the line number on the error, look in your code to see if you see what is wrong. Debugging Tips IT452 - Debugging Tips Main IT452 page Debugging Tips You should try all of these before banging your head against the wall.