> If all you want to do is make an element not be clickable, then the
> example holds up (as it's comment notes).
Dunno, if you aren't binding a real method at all, to me adding a fake
method just to return false is more esoteric/semantically unclear than
removing the `href` attribute or completely removing the <a> and
substituting plain text. (Me, I usually remove the href and also add
the not-allowed cursor if people are used to seeing a live link at
other times.)
> But if instead you want to attach a method from a class to an
> element and stop the event, it's esoteric to use it for that
> purpose...
I did agree from the top that stop() is the proper way, I'm just not
convinced that -- once you decide to return false instead -- there's
anything super-wrong with trying *not* to use a wrapper if it turns
out to be very concise (what do you think of Lewis' `returnFalse`
wrapper?).
Maybe the shortest way to "finalize false" with the smallest amount of
chaff and no extra methods and no extra event to manage:
onclick="return f() && false;"
addEvent('click',function(){return f() && false;})
Not saying I'm all about using these, but I don't see them as
esoteric. It's kind of a Catch-22 in that if you are used to using
return false, then you understand it as soon as you see it in the
event context... if you use e.stop() properly all the time, then
return false may pop out as an exception.
--Sandy
