> Then imho it should be the opposite...Elements methods should take > precedence over Array methods, because when we work with an elements > object, we work with an array of elements, not with any other things
It might seem like the more specific method should be called, but the paradigm (per Aaron, Moo dev) is to respect anything that is "already" on the native Array object, even if that method was added by Moo. This protects against collisions with a future ES standard that might add methods to the native. (And it isn't necessarily true that you don't want Array methods on Elements. The Array.contains() might be exactly what you want.) -- S.
