508 Commits

Author	SHA1	Message	Date
Brandon Aaron	92aac3abd6	Fixes memory leaks relating to events in IE with page unload and with jQuery methods remove, html and empty (#1610, #1618, #1697 and #1731). Also re-worked variable names to be more consistent with the core.	2007-10-06 17:04:20 +00:00
John Resig	beebbf8ba4	Safari 2 was having problems with the syntax used for the ready handling.	2007-10-01 14:14:09 +00:00
John Resig	1344a7fd50	Fixed the attribution for the DOM Ready fix - the previously used changes weren't significant.	2007-09-27 20:49:30 +00:00
Brandon Aaron	ee2efbe1e3	Fix for #1153	2007-09-27 18:09:23 +00:00
John Resig	6e8a8c5359	Converted jQuery to use the new DOM Ready technique (by checking scroll). A single setTimeout loop is used for both IE and Safari now. Fixex bugs #1320 and #1561.	2007-09-27 15:23:07 +00:00
John Resig	82eccdfcd0	Make sure that the right event type is always triggered (was causing problems with UI's event triggering).	2007-09-14 23:58:51 +00:00
John Resig	3a4e1233aa	Landing the new expando management code. Completely overhauls how data is associated with elements. ... Plugins will be most interested in: - jQuery.data(elem) -> Unique ID for the element - jQuery.data(elem, name) -> Named data store for the element - jQuery.data(elem, name, value) -> Saves a value to the named data store - jQuery.removeData(elem) -> Remove the expando and the complete data store - jQuery.removeData(elem, name) -> Removes just this one named data store jQuery's .remove() and .empty() automatically clean up after themselves. Once an element leaves a DOM document their events are no longer intact. Thus, statements like so: {{{ $("#foo").remove().appendTo("#bar"); }}} should be written like so: {{{ $("#foo").appendTo("#bar"); }}} in order to avoid losing the bound events.	2007-09-08 23:31:23 +00:00
John Resig	b4e23b5af0	Reorganzing the jQuery source (first phase).	2007-09-08 12:42:32 +00:00