| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
their events cloned by default.
|
|
|
|
| |
case not work. The optimization was fine. It was the unit test that was taking a short cut which caused it to fail after the optimization went in.
|
|
|
|
| |
updated after each release so its clear that a build is from which milestone; build.xml cleanup (removing uselss lite, docs, test and _with_plguins targets); deleted useless docs build files (replaced by wiki and wiki xml exporter and api browsers)
|
|
|
|
| |
jquery object was empty. The bug was created during the .val() refactoring for the javascript strict FF ticket.
|
| |
|
|
|
|
| |
like SELECT are not considered array-like (even though they really are).
|
| |
|
| |
|
|
|
|
| |
before testing it as an array. Otherwise it does a straight comparison during the filter test.
|
|
|
|
| |
innerHTML was done in some cases.
|
|
|
|
| |
jsonp: "callback" instead.
|
| |
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
code is only called when there is more than a single selector. So there should be no speed decrease in the current working cases. Only additional functionality for cases that used to fail.
|
|
|
|
| |
will now use a cross domain load the same as urls that start with "http".
|
|
|
|
| |
header cells in Opera
|
|
|
|
| |
added unit test for it.
|
|
|
|
| |
other types will be passed on to XMLHttpRequest.
|
|
|
|
| |
done. Before the code would immediately execute any scripts that weren't in subelements if no subelements prior had scripts in them (i.e. once any script was postponed they all were). This could cause inconsistent behavior. Since, at this time, we have to postpone some scripts it makes more sense to postpone them all.
|
| |
|
|
|
|
| |
hidden input.
|
|
|
|
| |
node and comment node safe.
|
|
|
|
| |
sometimes tossing errors that were being ignored and that caused a freeze in the test suite.
|
| |
|
|
|
|
| |
whole suite and its running on my local machine. I went ahead and put better error detection in for the test that is the culprit so it will keep going. It seems to do fine if I run it from a server. It gives xml.status as 0. Maybe this is the reason http://www.pearweb.com/javascript/XMLHttpRequest.html
|
|
|
|
| |
series of tickets including #1264 where the context of the DOM manipulation was a problem in xml and iframe documents.
|
|
|
|
|
|
|
| |
turned out most of them had already been implemented. The last ones necessary were in .domManip() with when a <table> was 'this' and for .text(). Adding these last changes seems to make dom and text manipulation in IE frames possible. Unit test cases were added as well.
In addition "submit.gif" was removed from the test suite index.html since it didn't exist.
|
| |
|
| |
|
| |
|
|
|
|
| |
context and if isn't default to other contexts.
|
|
|
|
| |
The JS error was fixed by checking to make sure 'opacity=' is in the filter before seeing what its value is.
|
| |
|
|
|
|
| |
just appending.
|
|
|
|
| |
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.
|