> I referred to passing with no params.
To prattle on: how could you merge getFirst and getElement without in
the end making it more complex to call the equivalent of getFirst() --
no params, as I and I'm sure many others usually call it -- in the new
regime?
Can't just make getElement() the same as getFirst() used to be -- BC
break, since getElement with no params currently returns null.
Gotta make people supply something new to getElement() in order to get
the same. You can require getElement('*'). It's not the hardest ever.
But then the framework is actually making the call *more* complex than
the DOM standard getFirstChild! That seems like bad juju.
-- S.
