Perhaps its just another case of RTFM but I might have a point here. Really.
I was using AJAX.NET and wanted to attach some silly handler to the “onmousedown” event of a link (“<a href”). I used the nice little $addHandler method in the following syntax:
$addHandler(myElement, “onmousedown”, myHandler);
And to my surprise it didn’t hook up anything.
I did what any developer would do, plunged back to the documentation and after a bit of a careful reading I saw the following line:
“The eventName parameter should not include the “on” prefix. For example, specify “click” instead of “onclick”.”
Now why should I care if I’m writing “onclick” or “click”. The convention used in browsers is “onclick”, after all that’s what you put on an element if you want to add an “onclick” handler in HTML.
Why would anyone want to break this convention. And even if you do decide to break it, adding a simple “if” or checking for the characters “on” at the start of the string and removing them would be nice.
Anyhow, I quickly changed the code to:
$addHandler(myElement, “mousedown”, myHandler);
and everything started to work wonderfully.
At least I’ve learned something new, that the eventName passed to the $addHandler function should not contain the “on” prefix. I also re-learned again that I should always RTFM, even the fine prints in the “Remarks” section.