![]() But anyway, back to the debugging exercise. mostly the errors are produced by sites with embedded ads. You'd be amazed at the number of sites out there which throw up Javascript errors. At this point, each time the browser encounters a Javascript error, it will pop up a message asking if you wish to debug. Unchecking these boxes will open you up to a world you had happily ignored for years - the world of Javascript errors. Go to the Advanced Tab and uncheck the boxes for Disabling script debugging ![]() This is done through "tools -> options" of course. The first step is to set IE to throw up Javascript errors, rather than swallowing them. But there are a couple of things you'll want to do. Visual Studio 20 have excellent support for debugging Javascript in Internet Explorer. I went from having to write println statements all over my code to trace values and execution paths, to being able to literally step through each line of code and see what the entire stack looked like! Woah! So what does this have to do with becoming a better web developer? Easy - if you're still using the alert("it worked") debugging style, it's time to graduate. It wasn't until my first real programming job, that I was introduced to an actual debugger, and it changed my world. If you're working in the Javascript world, you've likely found alert("it worked!"), which is the equivalent. I remember my days of debugging when I was an undergrad, where we had an extremely sophisticated debugger - (yes, most of my undergrad studies were done in Java). We'll start out with some debugging tips working with Javascript, but I'm going to do this as a multi-part series which will also include working with css, and other points of interest for web developers.ĭebugging is something that inevitably comes up, no matter what language you're using. My goal here is to give you tips to help you become the skill full ninja you've always wanted to be. Well, eventually I shook free from the unfounded notion that Javascript was bad, and have never looked back. As my HTML vocabulary grew, I started to see some of the really cool things you could do with DHTML, but most of it required that naughty Javascript. When I first started "web development" I knew nothing more than a handful of tags, and that "Javascript is bad!".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |