Thanks to all. That cleared up some stuff. By overhead I meant processing time and memory usage.
I hadn't seen the timeout call the error handler and thought it just canceled the call after looking at the code. Thanks! An option to add a timestamp to NOT cache ajax GETs is what I meant. It would be very helpful as an option. The comment about return false doing both preventDefault and stopPropagation is helpful. The docs could clarify that a bit. >>I build most my stuff for newer browsers and with "progressive enhancement" in mind. Unless you need to support IE < 6.0 or some of the older Netscapes, it shouldn't be too much of an issue. Well, what exact check are you doing before applying jquery? It will apply it to any browser. Even for example if you're letting in the new Safari/Konq/Opera maybe it dies on some obscure jquery call and is left hanging. Need to know the exact bugs to prevent that. Maybe I misunderstand but I thought some new browsers were failing parts of the test suite. I'm especially worried about ie 5.5 - yes, I know not supported so a bit off base here - and I could block it from jquery entirely myself but maybe I don't need to for what I'm doing. If I knew where it and especially new browsers fail I could plan. Looks like the know issues page is not really used. Any tips? Btw, can anyone suggest a good check for ie6+ and other new browsers? That might be noted in the docs as a "best practice" or maybe even built into jquery as a variable to set so it just returns the old "sorry, you're a loser" sort of thing for old browsers? I remember the old dynapi used to do that. Remember when dynapi was the ----?
