Re: [jQuery] jQuery 1.1.2
Thanks for valuable info!
But these aren't really attributes, at least in the HTML sense. They're
what I call custom properties, and a central plank of object-oriented
javascript t'boot. I use them all the time, but had no idea they were called
expandos (horrid name), or - more importantly - that they could cause
garbage collection problems.
I'll read up on this.
Thanks, again
Chris
On 3/1/07, Mike Alsup [EMAIL PROTECTED] wrote:
Please correct me if I'm understanding this the wrong way. Strings are
safe.
Object references are not.
That's correct. It's safe to store primitives in an expando because
the aren't reference counted for garbage collection. But objects are
trouble. An IE memory leak pattern is as simple as this:
var o = document.getElementById('A');
document.getElementById('A').myprop = o;
Jack Slocum has a good blog entry on avoiding memory leaks:
http://www.jackslocum.com/blog/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/
Mike
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Chris Ovenden
http://thepeer.blogspot.com
Imagine all the people / Sharing all the world
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
I believe so. As I said an expando attribute is basically any
non-standard attribute that gets added to an element (doesn't matter
how).
As Klaus notes, the memory leakage is only a problem in IE when the
attribute references other DOM elements (directly, or indirectly via
closures).
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
so any non standard attribute accessed simple as object.hello is an
expando? no matter if you call getAttribute or not??
On 2/28/07, Karl Rudd [EMAIL PROTECTED] wrote:
Err no, actually expandos refers to non-standard attributes that
get added to DOM elements. They expand the attributes that are
available on an element.
For instance adding an expando attribute called hello:
input type=submit value=blah hello=Hello world!
Because they're non-standard they can cause memory leak problems
under Internet Explorer if they refer to other DOM elements.
More info here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/expando.asp
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
Fil, did you ever get a definition of DOM 0 expandos...
they're the shortcuts that were provided with dom level 0, that are
short cuts for certain html(only) attributes, and collections of dom
nodes.
like
a.href is an 'expando' whereas a. a.getAttribute('href') is not.
and
document.forms is an expando whereas a.getElementsbyTagname('form') is
not.
I'm pretty sure thats what it means!
bonne chance!
On 2/28/07, Fil [EMAIL PROTECTED] wrote:
* Changed: Events are now internally stored in elem.$events rather
than elem.events (due to a nasty bug relating to DOM 0 expandos).
I'm translating this blog into French, but I can't figure how to
translate
this sentence. DOM 0 expandos ?
Anyway this is available at http://www.jquery.info/spip.php?article42
-- Fil
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
I'm confused. Are these expandos proprietory Microsoft attributes with a
specific meaning, or can it also apply to a non-standard attribute that I
may invent for a particular purpose (eg all collapsible elements on a page
might have a custom attribute collapsible=true)? If it's the latter, I
don't see how such attributes can reference anything at all, at least as far
as the DOM model is concerned. They're just strings.
Personally I avoid this kind of extra attribute; class is a pretty good
catch-all for most needs of this kind. I know you can make them valid HTML
by extending the DTD, but that seems like a lot of extra work for not much
gain.
Chris
On 3/1/07, Karl Rudd [EMAIL PROTECTED] wrote:
I believe so. As I said an expando attribute is basically any
non-standard attribute that gets added to an element (doesn't matter
how).
As Klaus notes, the memory leakage is only a problem in IE when the
attribute references other DOM elements (directly, or indirectly via
closures).
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
so any non standard attribute accessed simple as object.hello is an
expando? no matter if you call getAttribute or not??
On 2/28/07, Karl Rudd [EMAIL PROTECTED] wrote:
Err no, actually expandos refers to non-standard attributes that
get added to DOM elements. They expand the attributes that are
available on an element.
For instance adding an expando attribute called hello:
input type=submit value=blah hello=Hello world!
Because they're non-standard they can cause memory leak problems
under Internet Explorer if they refer to other DOM elements.
More info here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/expando.asp
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
Fil, did you ever get a definition of DOM 0 expandos...
they're the shortcuts that were provided with dom level 0, that are
short cuts for certain html(only) attributes, and collections of dom
nodes.
like
a.href is an 'expando' whereas a. a.getAttribute('href') is not.
and
document.forms is an expando whereas a.getElementsbyTagname('form')
is not.
I'm pretty sure thats what it means!
bonne chance!
On 2/28/07, Fil [EMAIL PROTECTED] wrote:
* Changed: Events are now internally stored in elem.$events
rather
than elem.events (due to a nasty bug relating to DOM 0
expandos).
I'm translating this blog into French, but I can't figure how to
translate
this sentence. DOM 0 expandos ?
Anyway this is available at
http://www.jquery.info/spip.php?article42
-- Fil
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Chris Ovenden
http://thepeer.blogspot.com
Imagine all the people / Sharing all the world
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
@ [EMAIL PROTECTED] : Fil, did you ever get a definition of DOM 0 expandos... Now I got plenty, thanks :) -- Fil ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Expandos are not proprietary to Microsoft. They are custom attributes. For
instance:
var oDiv = document.getElementById('myDiv');
oDiv.collapsible = true; // safe expando
var oSpan = document.getElementById('mySpan');
oDiv.relatedSpan = oSpan; // potentially dangerous expando
oDiv.relatedSpanId = oSpan.id; // safe expando
Please correct me if I'm understanding this the wrong way. Strings are safe.
Object references are not. I haven't had time to read the MSDN article from
the previous reply, but I'm pretty sure this is what they're talking about.
Brian.
On 3/1/07, Chris Ovenden [EMAIL PROTECTED] wrote:
I'm confused. Are these expandos proprietory Microsoft attributes with a
specific meaning, or can it also apply to a non-standard attribute that I
may invent for a particular purpose (eg all collapsible elements on a page
might have a custom attribute collapsible=true)? If it's the latter, I
don't see how such attributes can reference anything at all, at least as far
as the DOM model is concerned. They're just strings.
Personally I avoid this kind of extra attribute; class is a pretty good
catch-all for most needs of this kind. I know you can make them valid HTML
by extending the DTD, but that seems like a lot of extra work for not much
gain.
Chris
On 3/1/07, Karl Rudd [EMAIL PROTECTED] wrote:
I believe so. As I said an expando attribute is basically any
non-standard attribute that gets added to an element (doesn't matter
how).
As Klaus notes, the memory leakage is only a problem in IE when the
attribute references other DOM elements (directly, or indirectly via
closures).
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
so any non standard attribute accessed simple as object.hello is an
expando? no matter if you call getAttribute or not??
On 2/28/07, Karl Rudd [EMAIL PROTECTED] wrote:
Err no, actually expandos refers to non-standard attributes that
get added to DOM elements. They expand the attributes that are
available on an element.
For instance adding an expando attribute called hello:
input type=submit value=blah hello=Hello world!
Because they're non-standard they can cause memory leak problems
under Internet Explorer if they refer to other DOM elements.
More info here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/expando.asp
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
Fil, did you ever get a definition of DOM 0 expandos...
they're the shortcuts that were provided with dom level 0, that
are
short cuts for certain html(only) attributes, and collections of
dom
nodes.
like
a.href is an 'expando' whereas a. a.getAttribute('href') is not.
and
document.forms is an expando whereas a.getElementsbyTagname('form')
is not.
I'm pretty sure thats what it means!
bonne chance!
On 2/28/07, Fil [EMAIL PROTECTED] wrote:
* Changed: Events are now internally stored in elem.$events
rather
than elem.events (due to a nasty bug relating to DOM 0
expandos).
I'm translating this blog into French, but I can't figure how to
translate
this sentence. DOM 0 expandos ?
Anyway this is available at http://www.jquery.info/spip.php?article42
-- Fil
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Chris Ovenden
http://thepeer.blogspot.com
Imagine all the people / Sharing all the world
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Please correct me if I'm understanding this the wrong way. Strings are safe.
Object references are not.
That's correct. It's safe to store primitives in an expando because
the aren't reference counted for garbage collection. But objects are
trouble. An IE memory leak pattern is as simple as this:
var o = document.getElementById('A');
document.getElementById('A').myprop = o;
Jack Slocum has a good blog entry on avoiding memory leaks:
http://www.jackslocum.com/blog/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/
Mike
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
John, is it possible for the packed version to have a trailing semi-colon at the end? I get errors for the script I include after jquery if this isn't in place. Cheers and thanks for another great release, Chris ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
* Changed: Events are now internally stored in elem.$events rather than elem.events (due to a nasty bug relating to DOM 0 expandos). I'm translating this blog into French, but I can't figure how to translate this sentence. DOM 0 expandos ? Anyway this is available at http://www.jquery.info/spip.php?article42 -- Fil ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
I've noticed a problem in Safari too, this time with the datePicker plugin (also written by Kelvin - sorry!). When clicking the date picker icon, Safari immediately crashes every time when using the 1.1.2 release. However, I've tested with every single nightly build, from Feb 18 to Feb 28, and they all work perfectly. So, I don't know what's different in the released version?? I thought it might be a packing problem, but the problem also exists with the uncompressed file. All very strange... Seb On 28 Feb 2007, at 07:22, Jonathan Bloomer wrote: Just to let you know the latest release seems to have caused an issue with the jScrollpane plugin whereby it crashes Safari on mac, for now I would stick with the previous release of jQuery until the plugin has been updated. I have notified Kelvin of the problem, hope he can fix it it's a great plugin! ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
nice to see a bug fix release :) though atleast one bug is still in.. that`s the fadein and fadeout of a div in internet explorer.. it moves a little when those actions are done in IE (6) 2007/2/28, Seb Duggan [EMAIL PROTECTED]: I've noticed a problem in Safari too, this time with the datePicker plugin (also written by Kelvin - sorry!). When clicking the date picker icon, Safari immediately crashes every time when using the 1.1.2 release. However, I've tested with every single nightly build, from Feb 18 to Feb 28, and they all work perfectly. So, I don't know what's different in the released version?? I thought it might be a packing problem, but the problem also exists with the uncompressed file. All very strange... Seb On 28 Feb 2007, at 07:22, Jonathan Bloomer wrote: Just to let you know the latest release seems to have caused an issue with the jScrollpane plugin whereby it crashes Safari on mac, for now I would stick with the previous release of jQuery until the plugin has been updated. I have notified Kelvin of the problem, hope he can fix it it's a great plugin! ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Mark - Yep, we have fixes for those animation bugs, but we're in the process of testing them more (after which we'll release them). --John On 2/28/07, Mark [EMAIL PROTECTED] wrote: nice to see a bug fix release :) though atleast one bug is still in.. that`s the fadein and fadeout of a div in internet explorer.. it moves a little when those actions are done in IE (6) 2007/2/28, Seb Duggan [EMAIL PROTECTED]: I've noticed a problem in Safari too, this time with the datePicker plugin (also written by Kelvin - sorry!). When clicking the date picker icon, Safari immediately crashes every time when using the 1.1.2 release. However, I've tested with every single nightly build, from Feb 18 to Feb 28, and they all work perfectly. So, I don't know what's different in the released version?? I thought it might be a packing problem, but the problem also exists with the uncompressed file. All very strange... Seb On 28 Feb 2007, at 07:22, Jonathan Bloomer wrote: Just to let you know the latest release seems to have caused an issue with the jScrollpane plugin whereby it crashes Safari on mac, for now I would stick with the previous release of jQuery until the plugin has been updated. I have notified Kelvin of the problem, hope he can fix it it's a great plugin! ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
wonderfull!! good luck with bug hunting/fixing 2007/2/28, John Resig [EMAIL PROTECTED]: Mark - Yep, we have fixes for those animation bugs, but we're in the process of testing them more (after which we'll release them). --John On 2/28/07, Mark [EMAIL PROTECTED] wrote: nice to see a bug fix release :) though atleast one bug is still in.. that`s the fadein and fadeout of a div in internet explorer.. it moves a little when those actions are done in IE (6) 2007/2/28, Seb Duggan [EMAIL PROTECTED]: I've noticed a problem in Safari too, this time with the datePicker plugin (also written by Kelvin - sorry!). When clicking the date picker icon, Safari immediately crashes every time when using the 1.1.2 release. However, I've tested with every single nightly build, from Feb 18 to Feb 28, and they all work perfectly. So, I don't know what's different in the released version?? I thought it might be a packing problem, but the problem also exists with the uncompressed file. All very strange... Seb On 28 Feb 2007, at 07:22, Jonathan Bloomer wrote: Just to let you know the latest release seems to have caused an issue with the jScrollpane plugin whereby it crashes Safari on mac, for now I would stick with the previous release of jQuery until the plugin has been updated. I have notified Kelvin of the problem, hope he can fix it it's a great plugin! ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Not sure if this is bug-related or not, but if I try to open the test page in the full release of 1.1.2 (test/index.htm) it crashes Safari (2.0.4) every time. FWIW. John Resig wrote: As always, if you have any questions or concerns with new release, please feel free to discuss it on the jQuery Mailing List. If you think you've spotted a bug, please add it to the bug tracker: http://dev.jquery.com/newticket Download Compressed JavaScript (Recommended Download!) http://jquery.com/src/jquery-1.1.2.pack.js Uncompressed JavaScript http://jquery.com/src/jquery-1.1.2.js Full Release (jQuery, Test Suite, Documentation) http://jquery.com/src/jquery-1.1.2.release.zip Build Files (Compile your own version of jQuery 1.1.2) http://jquery.com/src/jquery-1.1.2.build.zip -- View this message in context: http://www.nabble.com/jQuery-1.1.2-tf3306736.html#a9208560 Sent from the JQuery mailing list archive at Nabble.com. ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Fil, did you ever get a definition of DOM 0 expandos...
they're the shortcuts that were provided with dom level 0, that are
short cuts for certain html(only) attributes, and collections of dom
nodes.
like
a.href is an 'expando' whereas a. a.getAttribute('href') is not.
and
document.forms is an expando whereas a.getElementsbyTagname('form') is not.
I'm pretty sure thats what it means!
bonne chance!
On 2/28/07, Fil [EMAIL PROTECTED] wrote:
* Changed: Events are now internally stored in elem.$events rather
than elem.events (due to a nasty bug relating to DOM 0 expandos).
I'm translating this blog into French, but I can't figure how to translate
this sentence. DOM 0 expandos ?
Anyway this is available at http://www.jquery.info/spip.php?article42
-- Fil
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Err no, actually expandos refers to non-standard attributes that
get added to DOM elements. They expand the attributes that are
available on an element.
For instance adding an expando attribute called hello:
input type=submit value=blah hello=Hello world!
Because they're non-standard they can cause memory leak problems
under Internet Explorer if they refer to other DOM elements.
More info here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/expando.asp
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
Fil, did you ever get a definition of DOM 0 expandos...
they're the shortcuts that were provided with dom level 0, that are
short cuts for certain html(only) attributes, and collections of dom
nodes.
like
a.href is an 'expando' whereas a. a.getAttribute('href') is not.
and
document.forms is an expando whereas a.getElementsbyTagname('form') is not.
I'm pretty sure thats what it means!
bonne chance!
On 2/28/07, Fil [EMAIL PROTECTED] wrote:
* Changed: Events are now internally stored in elem.$events rather
than elem.events (due to a nasty bug relating to DOM 0 expandos).
I'm translating this blog into French, but I can't figure how to translate
this sentence. DOM 0 expandos ?
Anyway this is available at http://www.jquery.info/spip.php?article42
-- Fil
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Karl Rudd wrote: Err no, actually expandos refers to non-standard attributes that get added to DOM elements. They expand the attributes that are available on an element. For instance adding an expando attribute called hello: input type=submit value=blah hello=Hello world! Because they're non-standard they can cause memory leak problems under Internet Explorer if they refer to other DOM elements. More info here: http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/expando.asp Karl Rudd Karl, Thanks for the excellent explanation. When it comes to adding attributes, Primitives are your friend -- Mike Alsup. ~ Brice ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
so any non standard attribute accessed simple as object.hello is an
expando? no matter if you call getAttribute or not??
On 2/28/07, Karl Rudd [EMAIL PROTECTED] wrote:
Err no, actually expandos refers to non-standard attributes that
get added to DOM elements. They expand the attributes that are
available on an element.
For instance adding an expando attribute called hello:
input type=submit value=blah hello=Hello world!
Because they're non-standard they can cause memory leak problems
under Internet Explorer if they refer to other DOM elements.
More info here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/expando.asp
Karl Rudd
On 3/1/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
Fil, did you ever get a definition of DOM 0 expandos...
they're the shortcuts that were provided with dom level 0, that are
short cuts for certain html(only) attributes, and collections of dom
nodes.
like
a.href is an 'expando' whereas a. a.getAttribute('href') is not.
and
document.forms is an expando whereas a.getElementsbyTagname('form') is not.
I'm pretty sure thats what it means!
bonne chance!
On 2/28/07, Fil [EMAIL PROTECTED] wrote:
* Changed: Events are now internally stored in elem.$events rather
than elem.events (due to a nasty bug relating to DOM 0 expandos).
I'm translating this blog into French, but I can't figure how to translate
this sentence. DOM 0 expandos ?
Anyway this is available at http://www.jquery.info/spip.php?article42
-- Fil
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Karl Rudd schrieb: Err no, actually expandos refers to non-standard attributes that get added to DOM elements. They expand the attributes that are available on an element. For instance adding an expando attribute called hello: input type=submit value=blah hello=Hello world! Because they're non-standard they can cause memory leak problems under Internet Explorer if they refer to other DOM elements. I'd like to add here, that the risk of causing memory leaks only exists if you use expandos in scripts together with closures. Because the pattern of such circular references is not always easy to spot I avoid expandos like the plague. More information: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/IETechCol/dnwebgen/ie_leak_patterns.asp -- Klaus ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
[jQuery] jQuery 1.1.2
Hi Everyone -
The release of jQuery 1.1.2 is upon us! This is a another bug fix
release. We've fixed a number of outstanding issues. The fixes have
been tested well, so there shouldn't be any regressions (knock on
wood). The most noticeable issue that was resolved was related to
animation flickers when doing a slideDown.
It is highly recommended that you upgrade.
As always, if you have any questions or concerns with new release,
please feel free to discuss it on the jQuery Mailing List. If you
think you've spotted a bug, please add it to the bug tracker:
http://dev.jquery.com/newticket
Download
Compressed JavaScript (Recommended Download!)
http://jquery.com/src/jquery-1.1.2.pack.js
Uncompressed JavaScript
http://jquery.com/src/jquery-1.1.2.js
Full Release (jQuery, Test Suite, Documentation)
http://jquery.com/src/jquery-1.1.2.release.zip
Build Files (Compile your own version of jQuery 1.1.2)
http://jquery.com/src/jquery-1.1.2.build.zip
Bug Fixes
The most important bug fixes, relevant to this release, are as follows:
* Change: Event handlers (like element.onclick) are now removed when
no more functions are bound to the event.
* Fixed: DOM Manipulations for form elements.
* Fixed: jQuery.isFunction to return false on nodes.
* Fixed: jQuery.className.has, escaping regex characters in className
(for metadata)
* Fixed: an issue in IE where an event on a cloned element is fired
during a .clone() inside of an event handler.
* Fixed: IE ID selectors selecting by the name attribute.
* Changed: Events are now internally stored in elem.$events rather
than elem.events (due to a nasty bug relating to DOM 0 expandos).
* Changed: .attr('href') is now consistent in all browsers.
* Changed: @href is now consistent in all browsers.
* Fixed: the slideDown flickering bug.
* Fixed: Having a \r endline in $(...) caused a never-ending loop.
* Fixed: IE6 AJAX memory leak
* Fixed: bug in pushStack, reporting an element at [0] in a jQuery
object with length 0
Documentation
Additionally, the documentation has been back-ported out of the wiki
and into the API docs. All of the documentation resources have been
updated in respect to the 1.1.2 release.
Official Documentation:
* http://docs.jquery.com/
API Browsers:
* http://jquery.bassistance.de/api-browser/
* http://jquery.com/api/
Leading up to jQuery 1.1.3...
This may seem like a fairly light bug fix release, but we're gearing
up to the release of jQuery 1.1.3. A number of outstanding bugs (about
5-10) require significant changes to how jQuery works, internally
(specifically, in relation to events and animations). We want to make
*100% certain* that there are no regressions made to these important
pieces of code.
We have patches nearly ready (animation is ready, events is in the
works) - and when that's the case, we're going to release a preview of
the 1.1.3 code so that everyone can test against it.
Announcements:
* http://jquery.com/blog/2007/02/27/jquery-112/
* http://www.learningjquery.com/2007/02/jquery-112-released
--John
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Awesome work! Looking forward to giving this a spin.
--Erik
On 2/27/07, John Resig [EMAIL PROTECTED] wrote:
Hi Everyone -
The release of jQuery 1.1.2 is upon us! This is a another bug fix
release. We've fixed a number of outstanding issues. The fixes have
been tested well, so there shouldn't be any regressions (knock on
wood). The most noticeable issue that was resolved was related to
animation flickers when doing a slideDown.
It is highly recommended that you upgrade.
As always, if you have any questions or concerns with new release,
please feel free to discuss it on the jQuery Mailing List. If you
think you've spotted a bug, please add it to the bug tracker:
http://dev.jquery.com/newticket
Download
Compressed JavaScript (Recommended Download!)
http://jquery.com/src/jquery-1.1.2.pack.js
Uncompressed JavaScript
http://jquery.com/src/jquery-1.1.2.js
Full Release (jQuery, Test Suite, Documentation)
http://jquery.com/src/jquery-1.1.2.release.zip
Build Files (Compile your own version of jQuery 1.1.2)
http://jquery.com/src/jquery-1.1.2.build.zip
Bug Fixes
The most important bug fixes, relevant to this release, are as follows:
* Change: Event handlers (like element.onclick) are now removed when
no more functions are bound to the event.
* Fixed: DOM Manipulations for form elements.
* Fixed: jQuery.isFunction to return false on nodes.
* Fixed: jQuery.className.has, escaping regex characters in className
(for metadata)
* Fixed: an issue in IE where an event on a cloned element is fired
during a .clone() inside of an event handler.
* Fixed: IE ID selectors selecting by the name attribute.
* Changed: Events are now internally stored in elem.$events rather
than elem.events (due to a nasty bug relating to DOM 0 expandos).
* Changed: .attr('href') is now consistent in all browsers.
* Changed: @href is now consistent in all browsers.
* Fixed: the slideDown flickering bug.
* Fixed: Having a \r endline in $(...) caused a never-ending loop.
* Fixed: IE6 AJAX memory leak
* Fixed: bug in pushStack, reporting an element at [0] in a jQuery
object with length 0
Documentation
Additionally, the documentation has been back-ported out of the wiki
and into the API docs. All of the documentation resources have been
updated in respect to the 1.1.2 release.
Official Documentation:
* http://docs.jquery.com/
API Browsers:
* http://jquery.bassistance.de/api-browser/
* http://jquery.com/api/
Leading up to jQuery 1.1.3...
This may seem like a fairly light bug fix release, but we're gearing
up to the release of jQuery 1.1.3. A number of outstanding bugs (about
5-10) require significant changes to how jQuery works, internally
(specifically, in relation to events and animations). We want to make
*100% certain* that there are no regressions made to these important
pieces of code.
We have patches nearly ready (animation is ready, events is in the
works) - and when that's the case, we're going to release a preview of
the 1.1.3 code so that everyone can test against it.
Announcements:
* http://jquery.com/blog/2007/02/27/jquery-112/
* http://www.learningjquery.com/2007/02/jquery-112-released
--John
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Amazing. I have a demo tomorrow and the bug I have been trying to fix all day is weird flickering menus. Then I hit this page for the 20th time today and what do you know... John Resig wrote: The most noticeable issue that was resolved was related to animation flickers when doing a slideDown. It seems everyday I check up on JQuery, somebody contributes just the thing I was looking for. Thanks to John and everyone else involved for all the hard work! -- View this message in context: http://www.nabble.com/jQuery-1.1.2-tf3306736.html#a9198126 Sent from the JQuery mailing list archive at Nabble.com. ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] jQuery 1.1.2
Just to let you know the latest release seems to have caused an issue
with the jScrollpane plugin whereby it crashes Safari on mac, for now
I would stick with the previous release of jQuery until the plugin has
been updated. I have notified Kelvin of the problem, hope he can fix
it it's a great plugin!
On 28/02/07, John Resig [EMAIL PROTECTED] wrote:
Hi Everyone -
The release of jQuery 1.1.2 is upon us! This is a another bug fix
release. We've fixed a number of outstanding issues. The fixes have
been tested well, so there shouldn't be any regressions (knock on
wood). The most noticeable issue that was resolved was related to
animation flickers when doing a slideDown.
It is highly recommended that you upgrade.
As always, if you have any questions or concerns with new release,
please feel free to discuss it on the jQuery Mailing List. If you
think you've spotted a bug, please add it to the bug tracker:
http://dev.jquery.com/newticket
Download
Compressed JavaScript (Recommended Download!)
http://jquery.com/src/jquery-1.1.2.pack.js
Uncompressed JavaScript
http://jquery.com/src/jquery-1.1.2.js
Full Release (jQuery, Test Suite, Documentation)
http://jquery.com/src/jquery-1.1.2.release.zip
Build Files (Compile your own version of jQuery 1.1.2)
http://jquery.com/src/jquery-1.1.2.build.zip
Bug Fixes
The most important bug fixes, relevant to this release, are as follows:
* Change: Event handlers (like element.onclick) are now removed when
no more functions are bound to the event.
* Fixed: DOM Manipulations for form elements.
* Fixed: jQuery.isFunction to return false on nodes.
* Fixed: jQuery.className.has, escaping regex characters in className
(for metadata)
* Fixed: an issue in IE where an event on a cloned element is fired
during a .clone() inside of an event handler.
* Fixed: IE ID selectors selecting by the name attribute.
* Changed: Events are now internally stored in elem.$events rather
than elem.events (due to a nasty bug relating to DOM 0 expandos).
* Changed: .attr('href') is now consistent in all browsers.
* Changed: @href is now consistent in all browsers.
* Fixed: the slideDown flickering bug.
* Fixed: Having a \r endline in $(...) caused a never-ending loop.
* Fixed: IE6 AJAX memory leak
* Fixed: bug in pushStack, reporting an element at [0] in a jQuery
object with length 0
Documentation
Additionally, the documentation has been back-ported out of the wiki
and into the API docs. All of the documentation resources have been
updated in respect to the 1.1.2 release.
Official Documentation:
* http://docs.jquery.com/
API Browsers:
* http://jquery.bassistance.de/api-browser/
* http://jquery.com/api/
Leading up to jQuery 1.1.3...
This may seem like a fairly light bug fix release, but we're gearing
up to the release of jQuery 1.1.3. A number of outstanding bugs (about
5-10) require significant changes to how jQuery works, internally
(specifically, in relation to events and animations). We want to make
*100% certain* that there are no regressions made to these important
pieces of code.
We have patches nearly ready (animation is ready, events is in the
works) - and when that's the case, we're going to release a preview of
the 1.1.3 code so that everyone can test against it.
Announcements:
* http://jquery.com/blog/2007/02/27/jquery-112/
* http://www.learningjquery.com/2007/02/jquery-112-released
--John
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
