Still Stuck?

Best javascript editor debugger Ajax website
↑

Main Page

Still Stuck?

If you've gotten to this page, you're probably frustrated. Don't think I'm being patronizing when I suggest you go take a break. Sometimes the best thing you can do for a problem is leave it alone for a minute. When you come back, the answer may be staring you in the face. If it's not, let me offer you these additional suggestions.

1.	Check again for typos. Revalidate your code (see page 345).
2.	Check the easy pieces first. So many times I've spent hours fiddling with an exciting new tag that just wouldn't work only to find that the problem was a typo in some tag that I'd used a thousand times before. Familiarity breeds contemptcheck the stuff you think you know really well before you harass the newcomers.
3.	Simplify the problem. Go back to the most recent version of your page that worked properly (which might be a blank page in some cases). Then test the page after adding each new element.
4.	Read through this chapter again.
5.	Check one final time for typos.
6.	Post the piece of code that doesn't work on my Question and Answer Forum (www.cookwood.com/html/qanda/). Be sure to include the relevant code (or a URL), a description of what is happening, and a description of what you think should be happening. People are very helpful there.

Figure 22.27. If you get stuck, try posting a question to my Question and Answer Forum (http://www.cookwood.com/html/qanda/). At press time, the Forum was not yet updated to reflect this Sixth Edition, but the URL will be the same.

[View full size image]

Best javascript editor debugger Ajax website
→