> Sanford: note that getElements takes any selector since MooTools Core 1.3
> (introduction of Slick).
I referred to passing with no params. If you always pass a selector,
the question of "merging" changing the signature to *require* a
selector is a non-issue.
> In the same way, getElement('> div') equals getFirst('div').
I think anytime you have to pass a new param/different param to make
two methods "equal," there can be very good reasons to keep them
separate.
I don't see them as redundant. But I never actually call getFirst with
a selector, other than a sometimes a type selector, I always use
getElements once I need a selector. If I were in the routine of
passing selectors, perhaps I would see more redundancy.
-- S.
