You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 27, 2020. It is now read-only.
Im wondering if this is a correct behaviour - if we take DOM element such as input as an example the onChange wont be called in this case.
I realize that this might be purely because onChange is assiociated with DOM event which is not fired in that case, but maybe this (and other similar components) shouldnt fire their onChangedValue~ handlers in case of "programmatic change". WDYT?
This is more of a general question rather than about this lib, but answer for that question affects expected behaviour of this one, so I thought it's a good place to discuss this.
The funny thing is that I have requested adding this 😂 and even I've implemented firing. After the time - it seems that it was a bad decision to make and it seems that downshift doesnt fire handlers for that case.
Im wondering if this is a correct behaviour - if we take DOM element such as input as an example the onChange wont be called in this case.
I realize that this might be purely because onChange is assiociated with DOM event which is not fired in that case, but maybe this (and other similar components) shouldnt fire their onChangedValue~ handlers in case of "programmatic change". WDYT?
This is more of a general question rather than about this lib, but answer for that question affects expected behaviour of this one, so I thought it's a good place to discuss this.
The funny thing is that I have requested adding this 😂 and even I've implemented firing. After the time - it seems that it was a bad decision to make and it seems that downshift doesnt fire handlers for that case.