I know you, and the other developers, are probably very busy with life and everything, but I was curious if there was any word on the new version of jQuery. I am highly interested in fixes for this Safari problem. :)
Also, thank you to John and everybody else for all of the hard work and genius being put into jQuery. - Ken On Aug 7, 8:53 am, "John Resig" <[EMAIL PROTECTED]> wrote: > This bug was found just after the 1.1.3.1 release - a ticket was > opened on it and a new version was provided to those that were > effected. The fix will be included in the upcoming 1.1.4 release > (which should be coming out today or tomorrow). > > --John
