> *shrug* Easy enough to add. Stick an extra key/value into your params.
of course, just found it strange it wasn't an option because a common problem and solution going back years. > Right, which is why I test on all the browsers in the projects specs. > Thankfully most of our projects are IE >= 6, Firefox >= 1.5, Safari >= > 2, and I usually test in the latest version of Opera. I'm on windows so no safari, and no ie5.5 either. Guess I could try everything on those standalone browsers but a known issues page per browser would be good. > Remember this is open source, if > you use it and find something wrong, try to make it right. :) no doubt, though you wouldn't want my code in there :-) I should submit the timestamp option for GET's as a bug, though. > :) Probably best to leave what to do to the programmer. There are just > too many possibilities and conditions to work through to automatically > decide "it won't run". That's why I suggested an option. Then easy to protect yourself entirely from early browsers rather than hunt for ways to check and code it in yourself. Thanks for the link but looks like overkill. I'll have to hunt for an object check. You know, if not x, then probably will have issues with jquery. createElement is bit lowball. If anyone has a suggestion... Thanks!
