Jake Zatecky

Unfortunately, it was never intended to allow duplicate values, as this component makes an assumption that each node has a different value. While allowing duplicate values could be seen as...

You should be able to identify movement via the `onChange` property. For example: ``` js onChange(selected) { const oldSelected = this.state.selected; if (selected.length < oldSelected.length) { // Items removed from...

Added `controlKey` parameter to the `onChange` function. Will be available in v2.4.0 release.

Can you elaborate on "single selection mode"? Do you mean only allowing the user to select a single item from the tree (like a radio button)? If so, then no,...

This would require a more complex render system or allow user-defined renderers for the selection box. This library makes many assumptions by letting the HTML `` element do the heavy-lifting....

Going to close this as a duplicate of #38, as this would best be done in userland provided that #38 ever landed.

Styles added for smaller viewports. The issue @ragepro describes is covered under another issue (#138) and affects Webkit and Chrome mobile devices.

Notable that this failure in behavior also requires `preserveSelectOrder` to be set.

I spent a fair bit of time today researching how to mitigate this issue. It appears there is no way to force Webkit and Chromium mobile browsers to render a...

I already detailed my findings above. Without replacing the native `select` HTML elements with something custom, this issue will persist. I am not keen on spending 20+ hours rewriting the...