New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jquery-typeahead as a npm package #170

Closed
running-coder opened this Issue Mar 22, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@running-coder
Owner

running-coder commented Mar 22, 2016

jquery-typeahead is now available as a npm package:
https://www.npmjs.com/package/jquery-typeahead

npm install jquery-typeahead

@running-coder running-coder added this to the 2.4.0 milestone Mar 22, 2016

running-coder added a commit that referenced this issue Mar 26, 2016

Version 2.4.0
Features
- #160 if onSubmit callback returns true, the form should be submitted with a regular browser submit
Fixes
- #166 Different browsers do not have the same behaviors when pressing "Esc" key when the input is focused
- #165 Submitting form with typeahead inside (hideLayout called multiple times)
- #161 Fixed missing X icon when using bootstrap css
Notes
- #170 jquery-typeahead as a npm package
- #169 Add basic unit tests
- Abandonned Dynamic Source Switching option. Would have to handle too many custom case, instead the sources should be loaded and a matcher function should be used

running-coder added a commit that referenced this issue Mar 26, 2016

Version 2.4.0
Features
- #160 if onSubmit callback returns true, the form should be submitted with a regular browser submit
Fixes
- #166 Different browsers do not have the same behaviors when pressing "Esc" key when the input is focused
- #165 Submitting form with typeahead inside (hideLayout called multiple times)
- #161 Fixed missing X icon when using bootstrap css
Notes
- #170 jquery-typeahead as a npm package
- #169 Add basic unit tests
- #148 Updated Typeahead AMD, please review requirejs_v1 example
- Abandonned Dynamic Source Switching option. Would have to handle too many custom case, instead the sources should be loaded and a matcher function should be used
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment