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
I have run into a scenario where a user has used KeyboardedInput, and then clicks on a button in my UI that causes the KeyboardedInput component to be unmounted, but this also triggers the KeyboardInput's HandleFocusLost function.
This results in a warning like so:
warning.js:33 Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op. Please check the code for the KeyboardedInput component.
In my local testing I have removed the setTimeout() wrapper on this line, and I no longer receive the warning. Does this setTimeout() wrapper serve a purpose?
The text was updated successfully, but these errors were encountered:
@etctschq I'll have to review the impact we looking at moving the deps to React v16 and doing a major release and releasing v1 now that we have alot more features and bugs squashed.
So it might be time also to review the logic of some of the setTimeout code too. It might need to clear timeout on componentWillUnmount.
I have run into a scenario where a user has used KeyboardedInput, and then clicks on a button in my UI that causes the KeyboardedInput component to be unmounted, but this also triggers the KeyboardInput's HandleFocusLost function.
This results in a warning like so:
In my local testing I have removed the setTimeout() wrapper on this line, and I no longer receive the warning. Does this setTimeout() wrapper serve a purpose?
The text was updated successfully, but these errors were encountered: