1.1.4 breaks Interface, firebug reports:
jQuery.easing[options.easing] is not a function
z.now = jQuery.easing[options.easing](p, n, firstNum, (last-firstNum),
options.duration);
jquery.js line 5214
help? thx.
Pops,
this problem occurred in jQuery because of the heavy usage of
closures, especially in the case of onreadystatechange (as explained
in the article posted in the jQuery ticket). It never occurred for
example in MooTools because the onreadystatechange handler is a class
method and not a
On Aug 28, 6:17 pm, digitarald [EMAIL PROTECTED] wrote:
The easiest fix, instead of using a
periodical checker which seems kind of weird on the first blush, is to
avoid closures during coding ...
Just for clarfication.
The idea of polling for non-atomic states is a Sync 101 violation.
On Aug 27, 11:31 am, John Resig [EMAIL PROTECTED] wrote:
YUI, Dojo, and jQuery all use this technique to avoid these leaks.
It's unavoidable otherwise.
John,
I'm curious. Been catching up of the technical issues and JS/DOM
framework, and it seems to me that a basic part of the issues is
Hi John,
I do believe this leak has been fixed since quite a while ago
(understatement): http://dev.mootools.net/ticket/5
-Olmo M.
P.S. I had sent this email, but noticed it wasn't added. Ignore
duplicates plz. :)
On Aug 25, 8:30 pm, John Resig [EMAIL PROTECTED] wrote:
I just took a look at
John,
I've been doing some digging to find that leak and I believe it had
been resolved since the 5th ticket in our Trac.
http://dev.mootools.net/ticket/5
I also don't encounter any leaks in my own tests.
-Olmo M.
On Aug 25, 8:30 pm, John Resig [EMAIL PROTECTED] wrote:
I just took a look at
Olmo -
That alone is not sufficient - that's what we originally used as well.
See this ticket:
http://dev.jquery.com/ticket/991
and this blog post:
http://alex.dojotoolkit.org/?p=528
YUI, Dojo, and jQuery all use this technique to avoid these leaks.
It's unavoidable otherwise.
--John
On
The front page of the jquery site still shows 1.1.3.1. When might
this be fixed to reflect the new version and new links?
On Aug 24, 1:46 am, John Resig [EMAIL PROTECTED] wrote:
Hi Everyone -
jQuery 1.1.4 has just been released! The full details of this release
can be found on the jQuery
Where? I see 1.1.4 on my end.
--John
On 8/27/07, Shelane [EMAIL PROTECTED] wrote:
The front page of the jquery site still shows 1.1.3.1. When might
this be fixed to reflect the new version and new links?
On Aug 24, 1:46 am, John Resig [EMAIL PROTECTED] wrote:
Hi Everyone -
jQuery
Shelane, we'll get that taken care of but in the interim, you can still
download v1.1.4 from the blog posting you mentioned in your link or from
SVN.
Rey
Shelane wrote:
The front page of the jquery site still shows 1.1.3.1. When might
this be fixed to reflect the new version and new
Shelane,
I just verified and I see v1.1.4 listed there. Please refresh your cache.
Rey
Shelane wrote:
The front page of the jquery site still shows 1.1.3.1. When might
this be fixed to reflect the new version and new links?
On Aug 24, 1:46 am, John Resig [EMAIL PROTECTED] wrote:
Hi
I've ported the test to: http://ibolmo.no-ip.info/sandbox/ajax-leaks.html
(note: it might be offline in a few days-- I'm moving :D).
Can't seem to reproduce the leaks. Let us know if you experience any.
Like I said, I had believed this had been taken cared of since the 5th
ticket. I did find it
Yep, I just did a force reload and it's showing properly. My bad.
On Aug 27, 9:20 am, Rey Bango [EMAIL PROTECTED] wrote:
Shelane,
I just verified and I see v1.1.4 listed there. Please refresh your cache.
Rey
Shelane wrote:
The front page of the jquery site still shows 1.1.3.1. When
I ran the test suite at http://jquery.com/test/ on my five browsers
(Firefox 2.0.0.6, MSIE 6, MSIE 7, Opera 9.23, and Safari (Windows)
3.0.3), and in four of them, 0 tests of 816 failed. In Safari,
however, 0 tests of 745 failed. What happened to the other 71
tests?
I'm new to jQuery, so
Hi John,
that's great news for everybody. We just updated the new builder for
the YAML CSS Framework to jQuery version 1.1.4 and it worked like a
charm. The builder runs more smooth now! Nice work. You can check it
out, it was originally build on version 1.1.3:
YAML (Yet Another Multicolumn
Hi John,
that's great news for everybody. We just updated the new builder for
the YAML CSS Framework to jQuery version 1.1.4 and it worked like a
charm. The builder runs more smooth now! Nice work. It was originally
build on version 1.1.3:
YAML (Yet Another Multicolumn Layout) Builder:
Hi Tom -
This is very cool, great work!
--John
On 8/25/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi John,
that's great news for everybody. We just updated the new builder for
the YAML CSS Framework to jQuery version 1.1.4 and it worked like a
charm. The builder runs more smooth now!
Pops schrieb:
So who knows what the developer of this code was thinking when he/she
set this value to 1. Maybe you do need it for animation. Maybe he had
yahoo finance running at the time and it mistakely thought that 1ms is
the Fastest Possible when it fact it is not. Zero ms is the
fastest.
WebKit nightlies and Safari 3 disregard any timers less than 10ms and
according to this article so does IE and Firefox. See the section titled
(3) JS Timeouts and Intervals here: http://webkit.org/blog/?p=96
--
Brandon Aaron
On 8/26/07, Jörn Zaefferer [EMAIL PROTECTED] wrote:
Pops schrieb:
I find slice very useful method.
I just wanted to post a little tutorial about selecting a range of
elements, but now, there's no need for that. No more filter().filter().
(beside that I made keyboard shortcut for that snippet).
--
Dragan Krstić krdr
http://krdr.ebloggy.com/
Couldn't you just use beforeSend to intercept the XMLHttpRequest
object and add your own callback handlers to it directly? You'll have
to put up with all of the aforementioned memory leak issues, but you'd
get access to all of the state changes that you're looking for...
--Erik
On 8/25/07,
Eric, anyone can come up with a solution.
But if we strictly talking about jQuery and using it in an optimized,
reliable, maximum support possible, then no.
I think the patch I illustrated resolves the issues.
Overall, my thoughts are:
1) Not defining the readystatechange, the protocol is
If only everything was so cut and dry.
--
Brandon Aaron
On 8/25/07, Pops [EMAIL PROTECTED] wrote:
Eric, anyone can come up with a solution.
But if we strictly talking about jQuery and using it in an optimized,
reliable, maximum support possible, then no.
I think the patch I illustrated
Brandon,
Very true. Not everything is so cut and dry.
This one, no doubt in mind, is not a good idea. I won't say that if I
didn't mean it, and I only say that because threads sychronization
design is one my areas of expertise.
I just took a look at prototype.js and mootools.js, neither are
On 8/25/07, Pops [EMAIL PROTECTED] wrote:
And my final point on this thread, the memory leak that I see is
related to clearing the XHR callback, which is understandable anyone
can originality miss that. But jQuery is not using the XHR callback.
So that should had not been an issue.
I just took a look at prototype.js and mootools.js, neither are
depended on a Lets hope if this best guess 13ms always works timer
concept.
Right, so they leak every single time you use them, both libraries are
quite naive about the issue of memory leaks.
If you're looking for some form of
On Aug 25, 9:30 pm, John Resig [EMAIL PROTECTED] wrote:
I just took a look at prototype.js and mootools.js, neither are
depended on a Lets hope if this best guess 13ms always works timer
concept.
Right, so they leak every single time you use them, both libraries are
quite naive about
Youpee!
-Original Message-
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of John Resig
Sent: vendredi 24 août 2007 9:47
To: jquery-en@googlegroups.com
Subject: [jQuery] jQuery 1.1.4: Faster, More Tests, Ready for 1.2
Hi Everyone -
jQuery 1.1.4 has just been
On 8/24/07, John Resig [EMAIL PROTECTED] wrote:
Hi Everyone -
jQuery 1.1.4 has just been released! The full details of this release
can be found on the jQuery blog:
http://jquery.com/blog/2007/08/24/jquery-114-faster-more-tests-ready-for-12/
Suffice it to say that some significant speed
John Resig wrote:
Hi Everyone -
jQuery 1.1.4 has just been released! The full details of this release
can be found on the jQuery blog:
http://jquery.com/blog/2007/08/24/jquery-114-faster-more-tests-ready-for-12/
Suffice it to say that some significant speed increases, test coverage
increases,
On 24/08/07, John Resig [EMAIL PROTECTED] wrote:
jQuery 1.1.4 has just been released!
Can you Digg it*?
http://digg.com/programming/jQuery_1_1_4_Faster_More_Tests_Ready_for_1_2
--
Best wishes,
Dave Cardwell.
* Sorry!
Dave Cardwell wrote:
On 24/08/07, John Resig [EMAIL PROTECTED] wrote:
jQuery 1.1.4 has just been released!
Can you Digg it*?
http://digg.com/programming/jQuery_1_1_4_Faster_More_Tests_Ready_for_1_2
Ha, Dave, you've been one second faster or something :-)
--Klaus
I notice the file size has crept up to 21kb from 19kb for 1.1.2.
--Erik
On 8/24/07, John Resig [EMAIL PROTECTED] wrote:
Hi Everyone -
jQuery 1.1.4 has just been released! The full details of this release
can be found on the jQuery blog:
John Resig wrote:
Hi Everyone -
jQuery 1.1.4 has just been released! The full details of this release
can be found on the jQuery blog:
http://jquery.com/blog/2007/08/24/jquery-114-faster-more-tests-ready-for-12/
Suffice it to say that some significant speed increases, test coverage
increases,
SeViR wrote:
I am confused, in the blog I read [...] new functionality have been
introduced. [...] slide() ...
but I download the direct link of jQuery and also, I updated from the
SVN trunk and build.
I don't see any slide() method, also I test with
$(#something).slide(1) but I get:
I am confused, in the blog I read [...] new functionality have been
introduced. [...] slide() ...
but I download the direct link of jQuery and also, I updated from the
SVN trunk and build.
I don't see any slide() method, also I test with
$(#something).slide(1) but I get:
.slide is not a
On 8/24/07, Erik Beeson [EMAIL PROTECTED] wrote:
I notice the file size has crept up to 21kb from 19kb for 1.1.2.
And...?
this is great work... and more speed improvements? wow, that is just amazing
news.
Thanks for the great library john.
-GTG
On 8/24/07, Su [EMAIL PROTECTED] wrote:
On 8/24/07, Erik Beeson [EMAIL PROTECTED] wrote:
I notice the file size has crept up to 21kb from 19kb for 1.1.2.
It was never mentioned that there was a new .slide() function - where
did you read that?
--John
On 8/24/07, SeViR [EMAIL PROTECTED] wrote:
I am confused, in the blog I read [...] new functionality have been
introduced. [...] slide() ...
but I download the direct link of jQuery and also, I
Yeah, a little bit unfortunate - but adding in bug fixes has obligated
that we increase the file size. Thankfully, if you GZip jQuery, we're
only about 11k.
--John
On 8/24/07, Erik Beeson [EMAIL PROTECTED] wrote:
I notice the file size has crept up to 21kb from 19kb for 1.1.2.
--Erik
On
He might have misread the slice() function?
-Original Message-
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of John Resig
Sent: Friday, August 24, 2007 10:24 AM
To: jquery-en@googlegroups.com
Subject: [jQuery] Re: jQuery 1.1.4: Faster, More Tests, Ready for 1.2
Andy Matthews schrieb:
He might have misread the slice() function?
that's a 2.0 feature (or better shall be) ...
micha
Great job John!
I think you hit it on the nose on what was the primary focus -
optimization!
Questions:
Is this consided a beta, gamma or production release? I ask because I
don't see it announce at jquery.com at the moment of this posting.
If there is still an window for improvements, I
On Friday, August 24, 2007 1:47 AM John Resig said:
jQuery 1.1.4 has just been released! The full details of this release
can be found on the jQuery blog:
http://jquery.com/blog/2007/08/24/jquery-114-faster-more-tests-ready-for
-12/
Suffice it to say that some significant speed increases,
Fixed!
On 8/24/07, Chris W. Parker [EMAIL PROTECTED] wrote:
On Friday, August 24, 2007 1:47 AM John Resig said:
jQuery 1.1.4 has just been released! The full details of this release
can be found on the jQuery blog:
No, this is final - the blog post contains the full release notes:
http://jquery.com/blog/2007/08/24/jquery-114-faster-more-tests-ready-for-12/
Do you have any specific Ajax improvements?
--John
On 8/24/07, Pops [EMAIL PROTECTED] wrote:
Great job John!
I think you hit it on the nose on
You can still have slide by doing a plugin:
$.fn.slide = function(dir) {
if(!dir || dir == leftright) this.animate({width:'toggle'},
slow);
else if(dir == updown) this.animate({height:'toggle'}, slow);
}
$(#foo).slide(leftright);
$(#bar).slide(updown);
Infact maybe slideUp, slideDown and
Glen Lipka wrote:
I dont quite understad how the slice() feature works.
I am assuming this is zero based.
So let's say I had 10 DIVs.
0 1 2 3 4 5 6 7 8 9
What does the first and second number in the parens mean?
Apparently you do not need to have both.
And negative numbers mean
On Aug 24, 12:48 pm, John Resig [EMAIL PROTECTED] wrote:
No, this is final - the blog post contains the full release
notes:http://jquery.com/blog/2007/08/24/jquery-114-faster-more-tests-ready-...
Yes, a few mins after my post, I saw the jQuery.com page was updated.
Cool.
Do you have any
I dont quite understad how the slice() feature works.
I am assuming this is zero based.
So let's say I had 10 DIVs.
0 1 2 3 4 5 6 7 8 9
What does the first and second number in the parens mean?
Apparently you do not need to have both.
And negative numbers mean something.
Maybe someone
Thanks to everyone on the dev team for the new release!
@Klaus: are you planning to update your tabs plugin to the new
release? It uses eq(), which I understand are deprecated now.
Bernd
Bernd Matzner wrote:
Thanks to everyone on the dev team for the new release!
@Klaus: are you planning to update your tabs plugin to the new
release? It uses eq(), which I understand are deprecated now.
I'd rather work on UI Tabs aka Tabs 3 at the moment... :-)
But ok, I'll fix that, I only
I'd rather work on UI Tabs aka Tabs 3 at the moment... :-)
I heard that! Looking forward to it ;-)
But ok, I'll fix that, I only need to figure out a way to support both
1.1.4 and less than 1.1.4 versions.
I think it would be enough to post a notice on your tabs page about it
not working
The .eq() method wasn't removed in 1.1.4, it was deprecated. All that
means is that you should begin to transition away from it to thew new
.slice() method (since .eq() will be removed in jQuery 1.2). Yeah, we
definitely wouldn't want to break plugins on a minor release, like
that.
--John
On
On Aug 24, 8:31 pm, Klaus Hartl [EMAIL PROTECTED] wrote:
Bernd Matzner wrote:
Thanks to everyone on the dev team for the new release!
@Klaus: are you planning to update your tabs plugin to the new
release? It uses eq(), which I understand are deprecated now.
I'd rather work on UI Tabs
Ok, there is always a reasons for something. I appreiciate you taking
the timeout to share it.
I think the problem with that patch is that there are redundant
XmlHttpRequest callbacks per state.The proper coding would wait
for the state to change.
var lastState= -1;
var
Pops,
Ok, there is always a reasons for something. I appreiciate you taking
the timeout to share it.
One thing to keep in mind is that jQuery is intended to be a cross-browser
library. Just because the XHR object works one in one browser, does not mean
it works correctly in all the browsers on
57 matches
Mail list logo
