I noticed this has been happening since the new sprite optimization builds. Looks like the problem is somewhat alleviated by disabling setFocus on the button, but sometimes it still happens. If setFocus isn’t enabled then the display object continues to receive events.
http://www.youtube.com/watch?v=sl43nuZulU4 [import]uid: 27183 topic_id: 24178 reply_id: 324178[/import]