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
12ef255ffd
Added ajax error messages in the unit test suite because Safari was sometimes tossing errors that were being ignored and that caused a freeze in the test suite.
2007-12-06 23:23:10 +00:00
Jörn Zaefferer
d44e9451f7
Fix for #2002
2007-12-06 19:51:00 +00:00
David Serduke
be4a8c32ac
Safari sometimes stops in the test suite on the ajax section when I run the 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
2007-12-05 23:03:58 +00:00
David Serduke
1be5582039
Fixed #1419 where IE failed with .text() on an XML node. This is part of a series of tickets including #1264 where the context of the DOM manipulation was a problem in xml and iframe documents.
2007-12-05 05:01:46 +00:00
David Serduke
74a132d944
Fixed #1264 . If you read the bug there were many proposed changes. As it 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.
2007-12-05 00:26:13 +00:00
Brandon Aaron
c424e79ccb
Added another relative offset test
2007-12-04 21:29:28 +00:00
Brandon Aaron
f576ceeea9
Beginnings of the offset test suite
2007-12-04 20:51:16 +00:00
David Serduke
76e3a90153
Fixed #1763 by checking to see if .createElement() is available on the context and if isn't default to other contexts.
2007-12-04 19:37:03 +00:00
David Serduke
d938c6bbd6
Fixed #1438 where a filter could be set in IE but not have opacity in it. The JS error was fixed by checking to make sure 'opacity=' is in the filter before seeing what its value is.
2007-12-04 18:15:27 +00:00
David Serduke
aee221d33c
Fixed #1999 by replacing the 'no-cache' parameter if it is there instead of just appending.
2007-12-04 04:43:45 +00:00
David Serduke
701b072e1a
There was a disabled test in the ajax test suite which said there were too 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.
2007-12-04 01:51:07 +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
5039a4bc5b
Added enchancement for #1994 by adding two parameters to .stop() which give 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).
2007-11-30 21:36:49 +00:00
David Serduke
37902e86b1
Fixed a problem with changeset [3841] where a function could no longer be .extend()-ed.
2007-11-30 08:39:49 +00:00
David Serduke
4b8f6cdc86
Fixed #1557 , although it doesn't appear to be just an FF3 problem. In this 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.
2007-11-29 19:07:20 +00:00
David Serduke
b6d70a7ce3
Back out one of the changes from the previous commit that wasn't necessary to fix the bug and might not be desired.
2007-11-28 23:53:54 +00:00
David Serduke
95c0265486
Fixed #1908 by testing to make sure it isn't null before checking the nodeType.
2007-11-28 23:42:16 +00:00
David Serduke
ed7608d8ee
Fixed #1070 by converting all setAttribute() values to a string which is what all browsers but IE did. This will bring IE in line with the others and fix the bug.
2007-11-28 23:13:59 +00:00
David Serduke
3ae5fbc16a
Fixed #1701 by passing through the arguments as suggested.
2007-11-28 22:23:40 +00:00
David Serduke
5c6c99361f
Fixed #1714 by adding a default empty string if the value is falsey.
2007-11-28 16:38:34 +00:00
David Serduke
0a755f6ab3
Fixed #1599 as Brandon suggested to ignore negative values to width and 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.
2007-11-28 01:01:49 +00:00
Brandon Aaron
5e99807271
Fix for #1944 . Added nodeName and tagName to jQuery.props and tests for maxlength, defaultValue, selectedIndex, tagName and nodeName.
2007-11-19 16:07:44 +00:00
David Serduke
2e2a1b8910
Slightly altered a test that was causing IE7 in some cases to hard crash. 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.
2007-11-18 00:46:58 +00:00
David Serduke
264ffbc73b
Fixed #1074 where .html() was incorrectly changing the selected value of an option.
2007-11-17 22:09:51 +00:00
David Serduke
bf8f3fe094
Fix #1907 where the never-ending loop prevention used a coersion comparison 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.
2007-11-17 04:25:22 +00:00
David Serduke
e2ef3df86d
Fixed #1095 bug where radio buttons became unchecked during show(). Also 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.
2007-11-16 23:39:23 +00:00
David Serduke
084079d2fd
Fixed #1727 bug where :nth-child() was non-standard with CSS3 plus two minor white space changes in selector.js.
2007-11-16 19:01:53 +00:00
David Serduke
0a0990485e
Fixed #1822 bug where queue() didn't always default to type 'fx'.
2007-11-16 18:23:59 +00:00
David Serduke
1d299d375b
Fix for #1823 bug in animate {queue:false} plus a unit test.
2007-11-16 17:49:12 +00:00
John Resig
1ac9d6fbee
Added a fix for .noConflict(true) not reverting properly. Also added unit tests for noConflict.
2007-10-20 22:04:06 +00:00
John Resig
14b88f6019
Fix for bug #1546 where a deep copy was attempted of DOM elements (which isn't needed).
2007-10-17 23:35:57 +00:00
John Resig
e287007f6a
Added a fix for bug #1698 , in which injected scripts were executed out of order, in relation to the DOM.
2007-10-17 22:42:12 +00:00
Brandon Aaron
971840f343
Fixed .val(String) for select elements ( #1760 ) [Thanks Sam]
2007-10-12 12:51:07 +00:00
John Resig
ad1cef94bf
A fix for bug #1443 , where globalEval occurred asynchronously in Safari 2, provided by Andrea Giammarchi.
2007-10-01 20:15:20 +00:00
John Resig
b453257653
Disabled the Ajax tests from running locally.
2007-09-23 15:58:49 +00:00
John Resig
3dabd7ec30
Added .eq(Number) back in - I'm convinced that it's more useful than the .slice() replacement. lt/gt are still gone, though.
2007-09-15 03:08:46 +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
606b863eda
Fixed bug #1594 , #1565 , #1598 - all of which were concerning the improper execution of embedded scripts in IE and Safari.
2007-09-15 02:16:29 +00:00
John Resig
62d84e44ac
Added a fix for bug #1580 , where the query string was appended to the POST data, instead of being left alone.
2007-09-15 01:18:30 +00:00
John Resig
6d71a10ed2
Fix for bug #1600 - multiple selects were being serialized incorrectly.
2007-09-15 00:23:21 +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
John Resig
b4e23b5af0
Reorganzing the jQuery source (first phase).
2007-09-08 12:42:32 +00:00
