Just calling .stop() without arguments will FREEZE the animation.
For your usage case, that’s perfect, because you’re animating rollover “sliding” buttons that, when rolled over, begin to animate to move towards the right, and when you remove the mouse it should of course FREEZE at the exact location it was and THEN begin animating towards the neutral position again.

So, yes your article is PERFECT for ROLLOVERS and other similar cases.

HOWEVER, let’s say you use an onclick event to trigger toggling between a .slideUp()/.slideDown() combo on and element and the user spam-clicks it. Click things enough and the element will end up frozen in some inbetween state between the two animation locations.

The solution is to read the jQuery documentation: http://api.jquery.com/stop/

It says that if your GOAL is to ABORT the current animation and animate into some other state, the CORRECT thing to do is to call .stop(true, true) – what this does is that IMMEDIATELY finalizes the ongoing animation by setting all the CSS to their final properties that it had been animating towards (such as a .slideUp()) so that the element is in a known-good-state (fully rolled up)), before you try to apply your slidedown animation.

So, I repeat, the code above in your example SHOULD be .stop(true, true) for A LOT of cases.

Please update the article with this caveat because it’s a very high-ranked Google result and a lot of people get their information from here.

Basically, people need to compare .stop() and .stop(true, true) to see what they need for their specific case.

$("#nav").find("li").each(function() {
	var jq = $(this);
	var dl = jq.find("dl");
	if (dl.length > 0) {
		jq.hover(function() {
			dl.stop(true,true).slideDown("slow");
		}, function() {
			dl.delay(250).fadeOut("slow");
		});
	}
});

Thanks for writing this article 4 years ago!