Replies: 2 comments
-
While this works in regular browser correctly, is fails in Adobe Photoshop yielding wrong item as changed |
Beta Was this translation helpful? Give feedback.
-
Ok, so here is what happens. in react-select/packages/react-select/src/Select.tsx Line 1990 in 06e3488 onSelect is attached to each DOM node that corresponds to Option .
When filtering in Chrome, nodes get correctly removed and are not reused, so clicking on what is left calls the correct callback and correct item gets selected. Now the question is – is there any way I can re-trigger |
Beta Was this translation helpful? Give feedback.
-
I am running
react-select
in a bit odd environment – Adobe Photoshop UXP plugins, where they have their own implementation of javascript engine and not everything is working as expected.Following AsyncSelect example and doing exactly the same – filtering items when input is changed – gives wrong items selected.
For example, having options
1,2,3,4,5
in as initial values and filtering5
, gives1
as a result in onChanged callback, basically selecting whatever value is there in the original options array, by index.As this is likely not a bug in the react-select, still, why could this be the case?
Beta Was this translation helpful? Give feedback.
All reactions