PrimaryFeather/Starling-Framework — pull request #127 by RRAway (2012-06-19 12:54:34+00:00)
Title: Starling's event bubbling is not consistent with Flash's system following display list mutation

When bubbling display events, Starling evaluates the next target up the display tree with each bubble dispatch. This means that any children added during the dispatch will also get the event. Calling removeChild() has the potential to stop the event chain entirely (Which is pretty annoying when doing UI events - e.g. hiding windows).

In traditional Flash: the objects that will receive the bubbled event are decided at dispatch time. Any changes to the display tree during the dispatches will have no effect on the objects receiving the event. As Starling's goal is to be familiar to Flash developers I think this behavior should probably be made to be consistent.

This patch adjusts the bubbling system to calculate the list on the first dispatch - in keeping with Flash's normal behavior.