Commit graph

84 commits

Author SHA1 Message Date
Brandon Aaron c73eadf599 Fixed memory leak in IE with non-native event types 2007-12-21 04:53:33 +00:00
Brandon Aaron fde3d616ac Removed check to prevent event from being fixed twice. Unfortunately, in IE this is sometimes necessary with its global event object. Binding both a mousedown and mousemove event is an example. 2007-12-21 02:11:26 +00:00
Brandon Aaron bdd6aca209 Fixing #2081 2007-12-20 19:31:02 +00:00
David Serduke 0419455473 Changed the $(document).ready() code to try and solve some problems in Safari, Opera, and IE. 2007-12-20 06:00:01 +00:00
Brandon Aaron a7dfbb55d9 Short-circuit jQuery.event.fix if it has already fixed the current event object. 2007-12-19 18:35:58 +00:00
David Serduke 3bb82a34de Second part of the fix for #2071. An empty string "" was being sent to .bind() and when the events were being cleared it went in to an infinite recursive loop till memory was out. The test was !types in the function and changing it to types == undefined fixed the error. 2007-12-19 01:48:05 +00:00
David Serduke 1d7b7b94ef Changed CRLF end of lines to just LF. Other than that there were no changes in this commit. Try svn diff -x --ignore-eol-style -r 4224:4225 to see that. 2007-12-19 01:10:20 +00:00
Richard Worth 76c1889e22 Fixed #1887 - trigger fails if extra is not a function 2007-12-18 03:13:39 +00:00
Brandon Aaron d1b9ad3cdb Fixed #2069. The ready helper and shortcuts act the same. You can also still bind, unbind and trigger the ready event on the document element but doing so follows the events API unlike the ready helper method. 2007-12-17 20:22:53 +00:00
Brandon Aaron 45e4a52cdd Cleaned up mouseenter and mouseleave special events 2007-12-16 22:18:35 +00:00
David Serduke 859aa6c9df Changed window.frameElement to window == top because of some access denied errors when the iframe wasn't same origin. 2007-12-16 10:33:38 +00:00
David Serduke 97e98591aa Added code so an iframe in IE won't count on doScroll to determine if the dom is ready. We will probably have to do more investigation on a better (and consistant) method for inside an iframe in IE. 2007-12-16 10:08:53 +00:00
Brandon Aaron 7a6978b324 Renaming variables to be more consistent 2007-12-16 04:09:53 +00:00
David Serduke feb9051c0e Fixed #1781 for warnings created on load by FF javascript.options.strict == true. 2007-12-16 01:03:50 +00:00
Brandon Aaron b264f789b9 new special events api, ready is now a first class event that you can use bind, unbind or the ready helper, two new events: mouseenter and mouseleave, the hover helper method now uses mouseenter and mouseleave, bind and unbind can now take a space sperated list of event types 2007-12-15 05:55:33 +00:00
Brandon Aaron 540f9304a7 Fix for #2032 2007-12-11 03:17:44 +00:00
Brandon Aaron 91f1299f68 Fix for #1486. Prevent IE from throwing an error when triggering focus on hidden input. 2007-12-08 02:54:09 +00:00
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
David Serduke b26da08821 Fixed #1970 by returning true instead of false when the mouse moves over a sub-element. The side effect is the event will not stop default behavior and will propagate which it didn't used to. I could find no compelling reason to stop those things from happening. 2007-11-27 19:20:36 +00:00
Brandon Aaron e6a481e533 Fix for #1933 2007-11-19 16:15:51 +00:00
Brandon Aaron ab96367f12 Fix for #1925 and removed some unnecessary browser sniffing 2007-11-14 21:55:45 +00:00
Brandon Aaron ee52c89dc9 Fix for #1911 2007-11-14 15:06:48 +00:00
John Resig a2fc65fd32 From a suggestion by Diego, moved the jQuery.ready() call outside of the try{}catch() block for IE/Safari DOM Ready. 2007-10-15 17:55:54 +00:00
Brandon Aaron a5f95c88c1 Fix normalization of pageX and pageY event properties in IE (#1571). Thanks wizzud. 2007-10-06 21:00:37 +00:00
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
Renamed from src/event/event.js (Browse further)