On 10/25/06, Dave Methvin <[EMAIL PROTECTED]> wrote: > Brandon committed that change, but I wrote it. Unfortunately, I don't have > Mac here so I can't test with Safari.
But I ran it through the tests and such ... but didn't test with /n character. > > jQuery.trim only trims leading/trailing space, so the newlines between the > <li> elements would be untouched. If there are no newlines it works? > > Is it crashing right on line 1568, or is it lower down where it pulls the > elements out of arg? Yeah it isn't with jQuery.trim and it still appears to be on line 1568 as it doesn't even make it to that loop sometimes. > Perhaps it is dying on the "if" right below that? No reason for it to do > that but who knows. Instead of letting it fall into the loop replace line > 1568 (arg = div.childNodes) with this: > > for ( var n = 0; n < div.childNodes.length; n++ ) > r.push(div.childNodes[n]); > return; This is exactly what I had to do. Accessing div.childNodes directly makes Safari happier. Fix is in SVN Rev: 473. -- Brandon _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
