aboutsummaryrefslogtreecommitdiffstats
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* Fixed #2027 - make sure that cloned elements (within appendTo, etc.) have ↵John Resig2007-12-201-1/+6
| | | | their events cloned by default.
* Fixed a problem in the unit tests for IE where an optimization made the test ↵David Serduke2007-12-201-1/+2
| | | | 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.
* added version to all builds; changed current version to 1.2.2-pre - to be ↵Jörn Zaefferer2007-12-191-0/+48
| | | | 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)
* Fixed #2076 where .val() could return an array instead of undefined when the ↵David Serduke2007-12-181-1/+2
| | | | jquery object was empty. The bug was created during the .val() refactoring for the javascript strict FF ticket.
* width and height methods are now working properlyBrandon Aaron2007-12-182-6/+51
|
* Fixed #2070 by adding a test for !nodeType to isArrayLike so DOM elements ↵David Serduke2007-12-171-1/+1
| | | | like SELECT are not considered array-like (even though they really are).
* test for #2070Jörn Zaefferer2007-12-171-1/+4
|
* Test for #2069Jörn Zaefferer2007-12-171-0/+8
|
* Fixed #2062 by adding a check to see if the selector is array-like in .not() ↵David Serduke2007-12-171-1/+3
| | | | before testing it as an array. Otherwise it does a straight comparison during the filter test.
* Fixed #2037 where Opera would mis-state the value of 'display' after an ↵David Serduke2007-12-172-2/+9
| | | | innerHTML was done in some cases.
* Added a fix for bug #2020 - if you want to do data: {callback: "?"}, do ↵John Resig2007-12-171-3/+3
| | | | jsonp: "callback" instead.
* Adding data and removeData testsBrandon Aaron2007-12-161-1/+19
|
* new special events api, ready is now a first class event that you can use ↵Brandon Aaron2007-12-151-3/+28
| | | | 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
* Fixed #2046 by forcing the dataType to 'html' in the .load() function.David Serduke2007-12-141-10/+23
|
* Added a test case for $("<option>test</option>")[0].selected (bug #2050).John Resig2007-12-141-1/+3
|
* Fixed #1854 by using wizzud's suggestion. The only real difference is the ↵David Serduke2007-12-133-5/+10
| | | | 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.
* Fixed #1750 by adding a url that starts with "//" and is a dataType "script" ↵David Serduke2007-12-121-0/+22
| | | | will now use a cross domain load the same as urls that start with "http".
* Added more unit tests for offset. Fixed an offset issue relating to table ↵Brandon Aaron2007-12-125-3/+201
| | | | header cells in Opera
* Fixed a bug in clone where it wouldn't work on an XML node in IE. Also ↵David Serduke2007-12-121-1/+11
| | | | added unit test for it.
* Fix #1987 by only doing remote <script> type ajax with GET requests. All ↵David Serduke2007-12-111-0/+19
| | | | other types will be passed on to XMLHttpRequest.
* Fixed #1959 by postponing ALL script evaluations till the html insertion is ↵David Serduke2007-12-101-1/+2
| | | | 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.
* show is now element aware (#960)Brandon Aaron2007-12-082-1/+26
|
* Fix for #1486. Prevent IE from throwing an error when triggering focus on ↵Brandon Aaron2007-12-081-1/+11
| | | | hidden input.
* Fixed #1039 and #1733 by going through the core API and making them text ↵David Serduke2007-12-074-50/+146
| | | | node and comment node safe.
* Added ajax error messages in the unit test suite because Safari was ↵David Serduke2007-12-061-0/+44
| | | | sometimes tossing errors that were being ignored and that caused a freeze in the test suite.
* Fix for #2002Jörn Zaefferer2007-12-061-2/+5
|
* Safari sometimes stops in the test suite on the ajax section when I run the ↵David Serduke2007-12-051-5/+15
| | | | 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
* Fixed #1419 where IE failed with .text() on an XML node. This is part of a ↵David Serduke2007-12-051-3/+15
| | | | series of tickets including #1264 where the context of the DOM manipulation was a problem in xml and iframe documents.
* Fixed #1264. If you read the bug there were many proposed changes. As it ↵David Serduke2007-12-053-5/+34
| | | | | | | 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.
* Added another relative offset testBrandon Aaron2007-12-042-6/+5
|
* Added visual marker to absolute fixture for offset testingBrandon Aaron2007-12-041-2/+11
|
* Beginnings of the offset test suiteBrandon Aaron2007-12-044-0/+136
|
* Fixed #1763 by checking to see if .createElement() is available on the ↵David Serduke2007-12-041-4/+17
| | | | context and if isn't default to other contexts.
* Fixed #1438 where a filter could be set in IE but not have opacity in it. ↵David Serduke2007-12-041-1/+6
| | | | The JS error was fixed by checking to make sure 'opacity=' is in the filter before seeing what its value is.
* fixed jsdoc for equalsJörn Zaefferer2007-12-041-1/+1
|
* Fixed #1999 by replacing the 'no-cache' parameter if it is there instead of ↵David Serduke2007-12-041-1/+31
| | | | just appending.
* There was a disabled test in the ajax test suite which said there were too ↵David Serduke2007-12-041-5/+3
| | | | 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.
* Fixed [1993] although it actually wasn't a bug in the core but rather a ↵David Serduke2007-12-031-19/+46
| | | | | | | 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.
* Added enchancement for #1994 by adding two parameters to .stop() which give ↵David Serduke2007-11-302-13/+95
| | | | | | | 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).
* Fixed a problem with changeset [3841] where a function could no longer be ↵David Serduke2007-11-301-1/+9
| | | | .extend()-ed.
* Fixed #1557, although it doesn't appear to be just an FF3 problem. In this ↵David Serduke2007-11-292-0/+14
| | | | 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.
* Back out one of the changes from the previous commit that wasn't necessary ↵David Serduke2007-11-281-1/+1
| | | | to fix the bug and might not be desired.
* Fixed #1908 by testing to make sure it isn't null before checking the nodeType.David Serduke2007-11-281-1/+4
|
* Fixed #1070 by converting all setAttribute() values to a string which is ↵David Serduke2007-11-281-1/+9
| | | | what all browsers but IE did. This will bring IE in line with the others and fix the bug.
* Fixed #1701 by passing through the arguments as suggested.David Serduke2007-11-281-2/+6
|
* Fixed #1714 by adding a default empty string if the value is falsey.David Serduke2007-11-281-1/+3
|
* Fixed #1599 as Brandon suggested to ignore negative values to width and ↵David Serduke2007-11-282-0/+10
| | | | 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.
* Fix for #1944. Added nodeName and tagName to jQuery.props and tests for ↵Brandon Aaron2007-11-192-4/+13
| | | | maxlength, defaultValue, selectedIndex, tagName and nodeName.
* Slightly altered a test that was causing IE7 in some cases to hard crash. ↵David Serduke2007-11-181-2/+2
| | | | 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.
* Fixed #1074 where .html() was incorrectly changing the selected value of an ↵David Serduke2007-11-171-2/+6
| | | | option.