On 11/2/06, Brandon Aaron <[EMAIL PROTECTED]> wrote: > I had to back out of 522 as it started producing some problems that > the test suite didn't catch. It wouldn't fire a function passed in to > $() for me.
Okay ... so I've tried a different way. I added a test for a[0] == undefined instead of checking the a.length property. I don't know of a situation where a[0] would be anything else if it is a function being passed to jQuery. However, I also forgot completely about the .length property ... so hopefully someone can chime in and verfiy that a[0] will always be undefined if a function is passed in for 'a' or with another way to allow a nodelist that safari thinks is a function to fall through. http://brandon.jquery.com/testing/safari_node_lists/index.html -- Brandon Aaron _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
