<p dir="auto">Annoying problem where the Pop overs don't detect when they're going to be slightly hidden by the size of the viewport. In Tooltipsy and stuff, it detects the edges and moves the wrapper accordingly.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://camo.githubusercontent.com/8d16529db9111212d7ded67ff2fa3822de20c3dcbbaf972533f4f6ec657df257/68747470733a2f2f646c2e64726f70626f782e636f6d2f752f373332333039362f706f706f766572732e504e47"><img src="https://camo.githubusercontent.com/8d16529db9111212d7ded67ff2fa3822de20c3dcbbaf972533f4f6ec657df257/68747470733a2f2f646c2e64726f70626f782e636f6d2f752f373332333039362f706f706f766572732e504e47" alt="Popovers" data-canonical-src="https://dl.dropbox.com/u/7323096/popovers.PNG" style="max-width: 100%;"></a></p>
<p dir="auto">I've just seen that since the version 2.1.X typeahead comes with an AJAX option which it actually comes in handy on many projects since I always had to implement my own autocomplete due to the fact that I would need the data to be fetched as typed.</p>
<p dir="auto">The only thing that I think it would be nice to have is a debounce method on the keyup event. As with each letter typed there will be a query, imagine how much payload that means on the server ( the one that takes the query ), and if I type really fast about 3 to 6 letters, that means 6 queries.</p>
<p dir="auto">Sometimes you get the second last query result and sometimes ( if you use an external API ) the server might block your API key because of to many queries / second.</p>
<p dir="auto">I hope that a debounce method with an option to set the interval would be taken into consideration. I could just due it to my local file, but I think that a lot of devs would appreciate this option :)</p>