This doesn't seem like an issue with bind! or unify.
There are three separate points here to clarify:
1) I'm not sure what the story is using (event/on "h3" ...) since you shouldn't have anything nested under an <h3> tag.
2) The `on` function actually has some special handling that assumes the container element (i.e., the first argument) is populated with children from a unify call, and thus have data attached to the nodes.
If you just want a plain ol' event listener, use `on-raw`.
3) Event capturing has nothing to do with stopping propagation. When an event happens on an element (e.g., you click it), the event starts at the DOM root and moves down into the triggering node in the "capture" phase. Once it reaches the triggering node, it starts going back out to the root in the "bubble" phase. Typically you nab events in the bubbling phase.
I can't see your DOM structure, but my guess about why you're getting a loop is because you're using `on` instead of `on-raw` and the internal helper logic is checking each of h3's parents for attached data.
--
Kevin Lynagh
Keming Labshttp://keminglabs.com
888.502.1042