{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/d084e44bfe1566d87abf80d1f6c0b8a4?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d084e44bfe1566d87abf80d1f6c0b8a4","url":"https://api.github.com/users/johnnywengluu","login":"johnnywengluu","id":445841},"milestone":null,"labels":[{"name":"bug","color":"e10c02","url":"https://api.github.com/repos/etgryphon/stativus/labels/bug"}],"assignee":null,"updated_at":"2011-11-12T19:59:46Z","comments":2,"closed_at":"2011-11-12T19:59:46Z","url":"https://api.github.com/repos/etgryphon/stativus/issues/17","body":"I think I found a bug.\r\n\r\nI have two concurrent states which registers an event handler with the same name.\r\n\r\nHowever, when I fire the event, only one of them is triggered. I haven't returned \"true\" so the event should propagate.\r\n\r\nI have recreated this weird behavior here: http://jsfiddle.net/johnnywengluu/ythns/1/\r\n\r\n- When you click the button it will fire the event.\r\n- I have commented the event handler that isn't triggered.\r\n- I have commented the event handler that is triggered.\r\n- I have commented what section to delete for it to work.\r\n\r\nThis is a good example of how useful nested states are. If the nested states bug is fixed first, I can recreate this code so that it will be simpler to get the statechart. Would want the nested architecture too in my real app or else it is too much anti-DRY and high typo risk.","html_url":"https://github.com/etgryphon/stativus/issues/17","title":"BUG: Concurrent event handler isn't triggered","number":17,"id":2141271,"created_at":"2011-11-04T06:57:56Z"},"action":"closed"}