Ezequiel Rodriguez
Ezequiel Rodriguez
Sure. I will send a pull request.
@kylehood Thanks for reporting the issue. What version of IE is this happening in?
@miketamis Couldn't you just pass an `onKeyDown` prop to Typeahead, and check if `event.key === 'Enter'`?
Good point! How does `onDropdownOpen` and `onDropdownClose` sound?
@trickeyone Thanks for the feedback. I've added the props `onBlur`, `onDropdownOpen`, and `onDropdownClose` in `0.5.0`. Let me know if they work as expected. :rocket: Just as a note, `blur` is...
Interesting... I wonder if this line is the problem: https://github.com/ezequiel/react-typeahead-component/blob/master/src/components/typeahead.jsx#L78 I would imagine `new Date().getTime()` producing different values on the client and server.
@jamesjjk Can you re-test by removing the above line and using some hardcoded id instead?
@jamesjjk Sure! One question though: is `inputName` for the `name` attribute on the `input` element? ex: ``?
@jamesjjk I've published a new version `0.8.0`, which [attempts to fix the unique id issue](https://github.com/ezequiel/react-typeahead-component/blob/master/src/components/typeahead.jsx#L12-20), and adds the `inputName` prop. Can you test it out and let me know how...
@jamesjjk May I have the checksum error message?