Comments on: Ajax requests when users stop typing

By: Brian

Brian — Wed, 07 Apr 2010 00:26:08 +0000

As I smashed my head against the wall for the better part of an hour, I finally landed on the exact answer I needed. Brilliant.

By: Secundes

Secundes — Tue, 20 Oct 2009 08:58:38 +0000

Great, it solves my problem.
Thanks

By: brad

brad — Wed, 07 Oct 2009 20:12:43 +0000

I believe the buffer was needed only for a specific version of IE, maybe 6.5, but I don’t recall exactly. I can’t imagine why adding 100 ms to the timeout callback would cause multiple events to be fired. What event are you binding your callback to, the keyup?

On a related note, I have found that an additional feature is needed to ensure xhr callbacks are processed in the correct order. A local counter is needed on the object that increments every time your “interceptKeypress” is fired. Then when you call the xhr request function, you have to pass the current value of that counter, and then check it in the xhr callback to ensure what is passed in is the same as the current value of the counter. Without this I was seeing issues where the most recent xhr request would fire, get called back, and then a previously called request would come back afterwards and trump it.

By: Joe

Joe — Wed, 07 Oct 2009 20:03:22 +0000

I’m having much more success without the 100 ms interval on the setTimeout. Placed an alert() in the sendResponse for testing. With the buffer, I’m seeing multiple alert fires where I should not, however seems to work fine without that buffer. Any insight?

By: adamzap

adamzap — Wed, 27 Feb 2008 13:31:34 +0000

w00t just what I needed thanks

By: brad

brad — Fri, 30 Nov 2007 20:07:09 +0000

Ah, so it is. Fixed now, thanks.

By: ws

ws — Fri, 30 Nov 2007 14:55:58 +0000

Thanks for the code! I’ve been trying to do something like this for a while.

FYI. there is a small typo in your code. The second Date().getTime() is typed Date.getTime().

Again.. Thanks for the code.