{"action":"created","issue":{"url":"https://api.github.com/repos/zk/clojuredocs/issues/90","repository_url":"https://api.github.com/repos/zk/clojuredocs","labels_url":"https://api.github.com/repos/zk/clojuredocs/issues/90/labels{/name}","comments_url":"https://api.github.com/repos/zk/clojuredocs/issues/90/comments","events_url":"https://api.github.com/repos/zk/clojuredocs/issues/90/events","html_url":"https://github.com/zk/clojuredocs/issues/90","id":44483743,"number":90,"title":"Typing too fast breaks search bar","user":{"login":"amalloy","id":368685,"avatar_url":"https://avatars.githubusercontent.com/u/368685?v=3","gravatar_id":"","url":"https://api.github.com/users/amalloy","html_url":"https://github.com/amalloy","followers_url":"https://api.github.com/users/amalloy/followers","following_url":"https://api.github.com/users/amalloy/following{/other_user}","gists_url":"https://api.github.com/users/amalloy/gists{/gist_id}","starred_url":"https://api.github.com/users/amalloy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amalloy/subscriptions","organizations_url":"https://api.github.com/users/amalloy/orgs","repos_url":"https://api.github.com/users/amalloy/repos","events_url":"https://api.github.com/users/amalloy/events{/privacy}","received_events_url":"https://api.github.com/users/amalloy/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2014-09-30T18:40:15Z","updated_at":"2016-11-08T00:04:48Z","closed_at":"2016-11-08T00:04:48Z","body":"I typed \"->> [RET]\" into the search bar, and was shown the search results for \"-\". I can reproduce this behavior by typing a `-` character, waiting for the search results to update, and then quickly typing `>>` followed by `Enter`.\n"},"comment":{"url":"https://api.github.com/repos/zk/clojuredocs/issues/comments/259004153","html_url":"https://github.com/zk/clojuredocs/issues/90#issuecomment-259004153","issue_url":"https://api.github.com/repos/zk/clojuredocs/issues/90","id":259004153,"user":{"login":"zk","id":7194,"avatar_url":"https://avatars.githubusercontent.com/u/7194?v=3","gravatar_id":"","url":"https://api.github.com/users/zk","html_url":"https://github.com/zk","followers_url":"https://api.github.com/users/zk/followers","following_url":"https://api.github.com/users/zk/following{/other_user}","gists_url":"https://api.github.com/users/zk/gists{/gist_id}","starred_url":"https://api.github.com/users/zk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zk/subscriptions","organizations_url":"https://api.github.com/users/zk/orgs","repos_url":"https://api.github.com/users/zk/repos","events_url":"https://api.github.com/users/zk/events{/privacy}","received_events_url":"https://api.github.com/users/zk/received_events","type":"User","site_admin":false},"created_at":"2016-11-08T00:04:48Z","updated_at":"2016-11-08T00:04:48Z","body":"Took another look at this today. I fixed a bug where results can return out of order affection the quick lookup results, but otherwise it's working as intended in that the [RET] action on the search bar means 'navigate to the first autocomplete result'. The second list of results hasn't come back from the server so the first entry in the first list is navigated to.\r\n\r\nI think the problem stems when using the quick search bar as a pure navigation tool -- a user wants to type in the name of a core var, `map`, for example, be taken to the `clojure.core/map` page.\r\n\r\nIt's worth looking into. One option is to ship all the core var names with the page cljs and fill the autocomplete results from two sources: in-mem and server."}}
{"actor":{"display_login":"zk"}}