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
Because of the asynchronous nature of the two, it is possible that a rerender occurs whilst slate is applying operations locally. This has as a result that onChange wll be called with an inconsistent value.
What's the expected behavior?
value should be set either internally or through props only so that updates can correctly be queued in some way and race conditions do not occur.
The text was updated successfully, but these errors were encountered:
As of #3093 (which was just merged), I believe this issue is no longer applicable, because a lot has changed. I'm going through and closing out any potential issues that are not out of date with the overhaul. Thanks for understanding.
Do you want to request a feature or report a bug?
Bug
What's the current behavior?
setValue
is called in two places in the controller:slate/packages/slate/src/controllers/editor.js
Line 378 in 5b8a6bb
slate/packages/slate/src/controllers/editor.js
Line 98 in 5b8a6bb
Because of the asynchronous nature of the two, it is possible that a rerender occurs whilst slate is applying operations locally. This has as a result that
onChange
wll be called with an inconsistent value.What's the expected behavior?
value
should be set either internally or through props only so that updates can correctly be queued in some way and race conditions do not occur.The text was updated successfully, but these errors were encountered: