I tested using the unpacked version as well as the packed version and the problem exists in both. Unfortunately, there is no error message identifying a line number, since the symptom is that Safari immediately shuts down. A window with crash details pops up, asking me to send the info to Apple. The error details didn't point to a problem that a Web developer can easily address. It was some memory error related to JavaScript, if I remember correctly.
-Mike Chabot On 8/7/07, Gordon <[EMAIL PROTECTED]> wrote: > Regarding your specific problem, have you tried running the > uncompressed version of jQuery in place of the compressed version? > While it wouldn't be sensible to deploy it on a live site for obvious > reasons, using the uncompressed versions for testing has huge benefits > for debugging as it's a lot easier to determine where a failure > occured.
