[Bug 16491] Add simpler and better event registration system

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

--- Comment #10 from Jonas Sicking <jonas@sicking.cc> ---
I think there are at least 3 different phases that are useful to register for:

* capture-only: This is what you currently get if you pass "true" as 3rd
argument
  of addEventListener. Useful for overriding listeners on the target.
* target-and-bubble: This is what you currently get by default for bubbling
  events. This is useful for "click" events and the like to see if an event
  was targetted at a given subtree.
* target-only: This is useful for load events, or for checking that an element,
  and not its descendents is currently being hovered.


So rather than having a "capture: true/false" property, I think it might be
better to have a "phase: 'target'/'capture'/'targetbubble'" property. That also
makes the API easy to expand as we find use cases for more phase combinations,
like 'bubble' or 'targetcapture'.

An alternative would be to use something like:

phase: ["bubble", "target"]

But that seems like annoyingly much typing.

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

Received on Friday, 15 February 2013 07:47:07 UTC