Good qualifier, but you hit the nail on the head with “getting the job done already.” Combinations of HTML, CSS, and JavaScript often present several routes to the same solution. My rule of thumb has become “Does it work? In all browsers? Good, moving on.”

“not as flexible when it comes to adding more jQuery magic to the mix.”

And you’re absolutely right… that is… it’s not as flexible *at this altitude.* A level higher (or lower, you could make the case) on the abstraction ladder, and you’d find many ways to utilize a non-inlined callback for the form submission. But… then the argument becomes an architectural brow-beating, and not one of just getting the job done already.

At any rate, for the up-and-coming, jQuery-using crowd, you present several core concepts of jQuery form and function while at the same time applying the lessons to a real example – and that’s just cool.

However, that code is (a) a bit longer and (b) not as flexible when it comes to adding more jQuery magic to the mix.

As for the function scope of confirmDelete(), I was just keeping things simple, as most readers simply want a working solution. However technical background is always a good thing. Thanks for covering for my laziness.

There is another way to do this. The third argument of the jConfirm() function is just a callback. You could have defined the function with an arbitrary name (the signature of which will be specified by jConfirm) and passed the name of that function in instead. By convention however, jQuery-esque scripts always prefer to inline these things (following the Java tradition of anonymous listeners, etc.).

“Also note the position of confirmDelete(): outside of the jQuery “document ready” block. If you put it inside, it won’t work.”

Yep – if you defined confirmDelete() inside of document.ready(), then you would only be able to call confirmDelete() from within document.ready() – that’s just the nature of nested functions (which are supported by JavaScript, Python, et. a. – but not PHP as you’re used to).