That is awesome! Thank you very much, and I will keep my fingers
crossed for you. :)
On Aug 20, 11:18 am, "John Resig" <[EMAIL PROTECTED]> wrote:
> 1.1.4 will probably be released tonight, if I can resolve some of
> these final, sticky, bugs.
>
> --John
>
> On 8/20/07, ru <[EMAIL PROTECTED]> wrot
1.1.4 will probably be released tonight, if I can resolve some of
these final, sticky, bugs.
--John
On 8/20/07, ru <[EMAIL PROTECTED]> wrote:
>
> Anyone know when 1.1.1.4 is going to be released?
>
> On Aug 14, 4:12 pm, Ken <[EMAIL PROTECTED]> wrote:
> > I know you, and the other developers, are
Anyone know when 1.1.1.4 is going to be released?
On Aug 14, 4:12 pm, Ken <[EMAIL PROTECTED]> wrote:
> 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 f
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 b
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. T
On Aug 7, 2007, at 3:48 PM, Dan G. Switzer, II wrote:
Live sites should be running GZIP to compress static files--so
there's no
reason some should be running the pack version.
Agreed. Minified gzipped javascript is my choice.
--
Mika Tuupola http://www.appelsiini.net/
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
On 8/7/07, Mike Chabot <[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 l
> Is it happening with packed version only?
>From Mike Chabot's original email:
I performed my tests with both the packed version and the unpacked
version. The packed version caused the browser to crash more quickly.
With the unpacked version, I sometimes had to refresh the browser
window a coup
The website does report opera 9.x as a requirement, but so far I've
found nothing that doesn't work in Opera 8.x except for transparency
effects, and they fail gracefully without causing any browser crashes,
so I'd say the documentation is a little strict regardign
compatibility. As long as you d
On Aug 7, 2007, at 7:55 AM, Mike Chabot wrote:
Is it happening with packed version only?
--
Mika Tuupola http://www.appelsiini.net/~tuupola/
> > So, for my solution, I have a conditional that uses jQuery 1.1.3.1 for
> > Safari with version numbers 417 and higher, and jQuery 1.1.2 for
> > Safari versions between 312 and 416.
>
> How do you do that? If your code works with 1.1.2, why not use it and
> forget 1.1.3.1 until it's fixed? If
On Aug 7, 2:55 pm, "Mike Chabot" <[EMAIL PROTECTED]> wrote:
> jQuery 1.1.3.1 Safari Crashes
>
> After upgrading a high-traffic Web site from jQuery 1.1.2 to jQuery
> 1.1.3.1, some Safari users started reporting that the Web site would
> cause their browsers to crash. The crash would be that Safari
13 matches
Mail list logo
