Thank you for your question.
We have specifically mentioned that the function is dependent on the browser
, because different browsers behave differently and we need to attach the events to different elements in order for the desired behavior to be achieved.
As for the event names, the attachEventHandler()
function supports both ways of writing them. Click
, for example, will produce the same behavior. However, addExternalHandler
only accepts event names, explicitly written without
prefix - for example: click, mouseover, mouseout. I have tested those scenarios and have experienced no issues achieving the desired behavior.
I am attaching a sample scenario that I have run on my machine which produced no unexpected results. Could you please run it and see whether it is also causing any issues?
If the problem persists, could you please provide us with additional information regarding the problem, such as the browser you are currently using, its version, and any steps required to reproduce the issue? Also, the ticket info states that you are using controls as of 2013 Q1, is that correct?
I hope that the provided answer was satisfactory. We will be expecting your feedback in case you are still experiencing the issue. Should you have any other questions, do not hesitate to contact us.
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed