{"action":"created","issue":{"url":"https://api.github.com/repos/angular/material/issues/4380","labels_url":"https://api.github.com/repos/angular/material/issues/4380/labels{/name}","comments_url":"https://api.github.com/repos/angular/material/issues/4380/comments","events_url":"https://api.github.com/repos/angular/material/issues/4380/events","html_url":"https://github.com/angular/material/issues/4380","id":103964379,"number":4380,"title":"md-chips with autocomplete is broken in 0.10.1","user":{"login":"brianfeister","id":806536,"avatar_url":"https://avatars.githubusercontent.com/u/806536?v=3","gravatar_id":"","url":"https://api.github.com/users/brianfeister","html_url":"https://github.com/brianfeister","followers_url":"https://api.github.com/users/brianfeister/followers","following_url":"https://api.github.com/users/brianfeister/following{/other_user}","gists_url":"https://api.github.com/users/brianfeister/gists{/gist_id}","starred_url":"https://api.github.com/users/brianfeister/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brianfeister/subscriptions","organizations_url":"https://api.github.com/users/brianfeister/orgs","repos_url":"https://api.github.com/users/brianfeister/repos","events_url":"https://api.github.com/users/brianfeister/events{/privacy}","received_events_url":"https://api.github.com/users/brianfeister/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-08-31T00:02:14Z","updated_at":"2015-08-31T01:29:53Z","closed_at":null,"body":"md-chips: autocomplete demo does not work in 0.10.1.\r\n\r\n![screenshot](http://g.recordit.co/X71C89ceTt.gif)"},"comment":{"url":"https://api.github.com/repos/angular/material/issues/comments/136230056","html_url":"https://github.com/angular/material/issues/4380#issuecomment-136230056","issue_url":"https://api.github.com/repos/angular/material/issues/4380","id":136230056,"user":{"login":"brianfeister","id":806536,"avatar_url":"https://avatars.githubusercontent.com/u/806536?v=3","gravatar_id":"","url":"https://api.github.com/users/brianfeister","html_url":"https://github.com/brianfeister","followers_url":"https://api.github.com/users/brianfeister/followers","following_url":"https://api.github.com/users/brianfeister/following{/other_user}","gists_url":"https://api.github.com/users/brianfeister/gists{/gist_id}","starred_url":"https://api.github.com/users/brianfeister/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brianfeister/subscriptions","organizations_url":"https://api.github.com/users/brianfeister/orgs","repos_url":"https://api.github.com/users/brianfeister/repos","events_url":"https://api.github.com/users/brianfeister/events{/privacy}","received_events_url":"https://api.github.com/users/brianfeister/received_events","type":"User","site_admin":false},"created_at":"2015-08-31T01:29:53Z","updated_at":"2015-08-31T01:29:53Z","body":"Is it expected behavior that the `keydown` helper function for both `md-chips` and also `md-autocomplete` are fired here.  With my limited understanding of the inner-workings, it definitely looks like a problem of two components listening for the `keydown` event and not having some 3rd party mediator that controls which one goes first.  Essentially, the `<input>` element's value gets cleared by `md-autocomplete` before the event lifecycle of `md-chips` is complete, so when chips gets around to selecting an item, autocomplete has an empty value, therefore chips selects the item at index 0, which is nothing."}}