deac/jquery - Forgejo: Beyond coding. We Forge.

deac/jquery

Author	SHA1	Message	Date
David Serduke	ffbedf0262	Fixed #1039 and #1733 by going through the core API and making them text node and comment node safe.	2007-12-07 01:52:21 +00:00
David Serduke	66fbbec3bb	Fixed [1993] although it actually wasn't a bug in the core but rather a misunderstanding of how the extra function was supposed to work in jQuery.event.trigger(). That said, it seems more useful and robust for the code to work the way the ticket author thought it should work so this change was made. Now, if anything is returned from the extra function it will overwrite the return value of the event handlers. This should only effect custom events unless someone had an extra function that returned a value other than false which would have been ignored before.	2007-12-03 21:41:10 +00:00
David Serduke	3ae5fbc16a	Fixed #1701 by passing through the arguments as suggested.	2007-11-28 22:23:40 +00:00
John Resig	d5f2129ac4	Fixed an issue with the suite expecting a different result for the changed triggerHandler behavior.	2007-09-15 02:23:08 +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	6728e3cf74	Finished up some of the reorganization.	2007-09-08 12:46:01 +00:00