| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
many simultainous requests. I re-enabled it when I found a bug that might have been the cause of the failure instead and it seems to work fine. We can disable it again if that ends up not being the case.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
additional functionality. The first parameter clearQueue will clear the queue on the necessary DOM elements so all animation will stop. The second parameter will cause the currently playing animation to immediately complete including reseting original styles on show and hide and calling the callback function. If no parameters are passed it will work as it always did.
While adding unit testing I noticed the stop() unit test wasn't working correctly because the element was hidden so I fixed it and added more unit tests around the new functionality. I also added a cursor:pointer to the css (because for a long time I didn't know they were clickable).
|
| |
|
|
| |
.extend()-ed.
|
| |
|
|
| |
case, $.getJSON() wasn't working from a remote host. I went ahead and added a unit test then added the s.dataType == "json" test for a remote <script> load. The said that json was allowed but the dataType check was missing. This appears to have fixed the bug across all browsers.
|
| |
|
|
| |
to fix the bug and might not be desired.
|
| | |
|
| |
|
|
| |
what all browsers but IE did. This will bring IE in line with the others and fix the bug.
|
| | |
|
| | |
|
| |
|
|
| |
height css. The fix itself is slightly different as it was moved to .css() instead of staying in .attr() like in his patch. I decided there was less chance of incorrect behavior (like if someone had an XML file with a width attribute that could be negative). Also took out some unneeded white space while I was in there.
|
| |
|
|
| |
maxlength, defaultValue, selectedIndex, tagName and nodeName.
|
| |
|
|
| |
The test was setting .html() to many divs, some of which were inside other divs effectly deleting them from the DOM. I suspect this caused some instability and may only have been an IE7 with IEDevBar issue. The test still correctly tests the functionality of that unit test.
|
| |
|
|
| |
option.
|
| |
|
|
| |
which sometimes dropped values incorrectly. Also fixed a bug where on deep copies the target copied over itself (i = 2 addition). Last made code handle the case when a property might have a string in it that should be overwritten by an object.
|
| |
|
|
| |
added unit test and had to fix a selector test that was broken by the new testing div in test/index.html. Last made some whitespace changes.
|
| |
|
|
| |
white space changes in selector.js.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
tests for noConflict.
|
| |
|
|
| |
isn't needed).
|
| |
|
|
| |
order, in relation to the DOM.
|
| | |
|
| |
|
|
| |
provided by Andrea Giammarchi.
|
| | |
|
| |
|
|
| |
.slice() replacement. lt/gt are still gone, though.
|
| |
|
|
| |
triggerHandler behavior.
|
| |
|
|
| |
execution of embedded scripts in IE and Safari.
|
| |
|
|
| |
data, instead of being left alone.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
