Ok, pardon the link-bait title. If you are a regular reader of this blog you know that on some Fridays I do a simple puzzler. This is a coding challenge that - typically - only requires about 5 minutes to solve. Today I've decided to do something a bit different. Maybe it will work - maybe it won't.

As you know - I am a huge advocate of making use of the debugging tools that modern browsers provide. I can't tell you how often I get emails from people who say their code isn't working and have absolutely no idea why.

The goal of this challenge (and the others that may or may not follow) is to simply debug a broken web application. I'm going to provide a link to a web page. In this case, a simple form that asks for two numbers and does math on them with JavaScript. As I said, the application is broken, but how it is broken is the task you need to solve. To be clear, if you already know how to use your browser dev tools then this challenge is probably not for you. But I bet you work with a few people who don't know squat about their browser. Or maybe you're like me and primarily a Chrome user. This would be a great opportunity to try the tools in another browser. Heck, maybe you'll learn something in the process.

When you figure it out, describe the process you took in the comments below. Most likely people will reach the solution via the same method and that's perfectly fine.

Today's challenge is rather easy I think - but if folks dig this I promise to ramp it up next time: http://www.raymondcamden.com/demos/2013/aug/16/test.html