{"action":"opened","issue":{"url":"https://api.github.com/repos/harvesthq/chosen/issues/2580","repository_url":"https://api.github.com/repos/harvesthq/chosen","labels_url":"https://api.github.com/repos/harvesthq/chosen/issues/2580/labels{/name}","comments_url":"https://api.github.com/repos/harvesthq/chosen/issues/2580/comments","events_url":"https://api.github.com/repos/harvesthq/chosen/issues/2580/events","html_url":"https://github.com/harvesthq/chosen/issues/2580","id":144013102,"number":2580,"title":"UI hangs on really large lists","user":{"login":"mcclurem","id":236281,"avatar_url":"https://avatars.githubusercontent.com/u/236281?v=3","gravatar_id":"","url":"https://api.github.com/users/mcclurem","html_url":"https://github.com/mcclurem","followers_url":"https://api.github.com/users/mcclurem/followers","following_url":"https://api.github.com/users/mcclurem/following{/other_user}","gists_url":"https://api.github.com/users/mcclurem/gists{/gist_id}","starred_url":"https://api.github.com/users/mcclurem/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcclurem/subscriptions","organizations_url":"https://api.github.com/users/mcclurem/orgs","repos_url":"https://api.github.com/users/mcclurem/repos","events_url":"https://api.github.com/users/mcclurem/events{/privacy}","received_events_url":"https://api.github.com/users/mcclurem/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-28T16:04:06Z","updated_at":"2016-03-28T16:04:06Z","closed_at":null,"body":"Version 1.5.1;\r\nBrowsers tested: Chrome, Safari;\r\nassumed to apply universally\r\n\r\nWhen working with /truly/ large selects (20K elements), the responsiveness of filtering leaves a bit to be desired.\r\nI think two key aspects could be dramatically improved:\r\n1) when clicking to cause the select box to open, don't search every item with a blank regex, simply populate the complete list - this should reduce select-opening time dramatically and it's probably the most noticeable part of the user experience problem.\r\n2) When typing, the search should have the option to be debounced (ideally with config defined duration?) so that the user can type several characters before it actually starts searching. Possibly this could even be done intelligently based on the number of pre-existing matches before searching (if winnowing an already small list, don't debounce as long)\r\n\r\nI'm looking into implementation details myself but if one of the regulars around here sees how to easily add one or both of these and can bang it out (or point me towards where to do it) that would be great."}}