Dispatch to parents

Ok, here is the bubbling dispatchToParents method, with tests.
Took the liberty to add a little feature: stopPropagation set to true in payload by any ancestor stops further bubbling. If one ancestor needs to catch the event and do the job, why bother its ancestors (and waste time) with useless triggers? 

Cool feature is that since the same object is passed along as payload, data can easily be sent back to issuer or shared between ancestors. Feel free to improve or to let me know if I missed something.
 I thought `stopPropagation` was good for the same reason you have doubts! It’s nothing new to remember (everyone immediately  knows what it does), and since it’s used in a different context (no event object available, just a data payload), people should expect it to be used differently.

I know that it pollutes the data payload, but 1) it’s the user who puts it there, so it’s not done unknown to him, 2) it’s specific enough in the choice of terms that it’s unlikely to interfere with application logic.  I guess one could also decide that such flags mixed with user data  should always have something like a leading  underscore in their name to further reduce the likelihood of interference….

Any idea for a better term?