Steve Bush: +1

People, you don’t delegate anything! There is no “event handling” vs. “event delegating”. When you speak about “delegating events” you still handle events.
Events do bubble (many years now) i.e. browser propagates them through DOM - in which process you can “catch” and handle them. And all of this is happenning regardles of where you attach your event-handlers to, ragerdless of where you handle those events.

I used it so much that I should make my own scripts to handle that with selectors. I can actually handle also the “focus” and “blur” events cross-browser by implementing a small trick in the handling/fixing of events.

You can see my work on delegates here:

http://javascript.nwbox.com/NWEvents/

Look under Delegates to see the only example specific to this method bound to CSS3 Selectors.
Though my syntax is not that short compared to jQuery or similar, I think the idea is unique.

I was searching for “delegates” related to “onload” problems but was not able to find anywhere talking about the fact that “Event Delegation” can lead to avoid having to resort to “onload” or similar method to attach functionality to the page at initial startup.

You seem to have a deep knowledge of these techniques, I would like your suggestion and comments on my implementation and possible improvements.

Do you mind if I copy (with credits) some Delegation example to include on my site ?

$(‘a.remote’).remote(‘#place’, function() {
if (window.console && window.console.info) {
console.info(‘content loaded’);
}

});

$.ajaxHistory.initialize();