All "each" style callbacks should pass consistent arguments.

[cowboy]

logs what you'd expect. $('*').each(function( i, elem ){ console.log( i, elem ); });

hey, it's an undefined party and everyone's invited! $('*').fadeOut(function( i, elem ){ console.log( i, elem ); });

This metaphor is used in many, many places, and it should be consistent across jQuery.

In addition, I'd like to see a third argument passed, which is a reference to the initial collection being operated on - is that even possible?

[cowboy]

I meant:

// logs what you'd expect.  
$('*').each(function( i, elem ){ console.log( i, elem ); });  

// hey, it's an undefined party and everyone's invited!  
$('*').fadeOut(function( i, elem ){ console.log( i, elem ); });  

[andrew_]

+1 for Ben's suggestion of passing the initial collection.

[addyosmani]

I agree that this behavior should be consistent. Moving to patch.

[john]

I'm not completely convinced that it makes sense in this case - as it's not a synchronous loop - it's more akin to attaching an event that is fired when fadeOut is complete (and I don't think that events really make sense having this sort of thing).