[Bug 16491] Add simpler and better event registration system

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16491

--- Comment #12 from Jonas Sicking <jonas@sicking.cc> ---
Currently the event system has come up with both the distinction between
bubbling and non-bubbling events, as well as the distinction between bubbling
and capturing listeners, as a way to enable people to not have to write
"if(e.eventPhase != Event.X) return" at the beginning of the listener.

So at least previously we've gone to great lengths to avoid that.

I actually think that that was a good thing. Being able to set a flag at the
time of registration, rather than adding additional code in the listener, both
increases code readability of the listener (the listener can be more focused on
doing whatever action needs to be done rather than when to do it) as well as
code readability at the listener registration site (it's easy to see what types
of events the listener will listen to).

FWIW, one of the other big features of the new event registration system is the
Selector filter, which also just avoids having to type
"if(!e.target.matchesSelector('...')) return"

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 15 February 2013 19:15:29 UTC