This only happens when there is no node selected (like on first page load). After the first node is selected then the event starts firing as expected. Can work-around the problem by selecting a node on the server in the code-behind on first page load.