Christian Maughan Tegnér
Christian Maughan Tegnér
This may save you some time: https://www.npmjs.com/search?q=jsonml
>currently it isn't possible to render an item, so that the matching part is highlighted (e.g. bold formatted) You already have the current value, it's the same as `props.value`.
As I've [mentioned](https://github.com/reactjs/react-autocomplete/pull/281#issuecomment-346999939) [before](https://github.com/reactjs/react-autocomplete/issues/176#issuecomment-317516871), this is most likely due to a mismatch between what you are passing in as `props.items` and the render-tree that your `renderMenu` method is returning. This...
Just a heads-up (in case you're waiting for this PR to land): You can fully customize the dropdown menu by using `props.menuStyle` and `props.renderMenu`. We'll probably be removing most of...
The easiest solution is probably to cut/slice `items` before passing it to `Autocomplete`. You can control `items` entirely from the outside (i.e. sorting, filtering, etc) and specify that every item...
> if filtering should be done on the items list before it is passed to Autocomplete, what is the point of exposing shouldItemRender? Yeah, you're sort of hitting an edge...
@marekolszewski this probably won't happen, as the goal is to move away from doing manipulations to `items` inside `Autocomplete`. As I said above, it's fairly easy to simply limit the...
Can you produce a fix for this? I've tried a couple of different attempts, but I keep coming up short because of how React delegates events. The implicit click handler...
Thanks for reporting this! I've started work on a fix, but sadly it will be very messy. I also notices that the current restore-scroll behaviour does not work as expected...
@vinhboy I'm afraid the entire logic needs a rethink. I hope to have time to address it soon, but I can't say for sure when this may be completed. If...