Impact and implications of broken .selector property
$('a1,a2').find('b1,b2').selector;
//RESULTS: "a1,a2 b1,b2"
//DESIRED: "a1 b1,a1 b2,a2 b1,a2 b2"
I would have thought this problem would break .live(), but apparently it doesn't. (I haven't stepped through the implementation of .live() well enough to understand why not.)
I have a patch available that fixes this behavior (test for comma in either selector; if either exists, split both on comma and combine) but the performance impact is non-negligible.
a) Where is the .selector property used internally, that this currently-broken behavior would exhibit as a bug?
b) How important is it to handle this edge case, when it would slightly slow down every call to .find()?