- Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
- Already on GitHub?
- Sign in to your account
@FilipeNevola: Subscribe to this github issue to be up-to-date about what is next in #reactjs (16.3 and 16…
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Async, expires within ~1 second. If a subsequent interactive event is fired before an earlier one has flushed, the earlier one is synchronously flushed before processing the incoming one.
Used for any event that is the result of a discrete user interaction. In other words, interactive events are events that cannot be debounced without affecting the terminal state. So a click event is interactive, but a scroll event is not.
in synchronous mode. Updates are flushed before React yields back to the browser.
Used for controlled components, where the state of the DOM must always be in sync with React’s internal state.
, promise handlers, etc.
New component API. We’re holding off on this until we’re closer to “feature complete,” a phrase which here means “having implemented async rendering and bytecode compilation.”
method. It would take lots of effort to migrate, mostly because of class instance methods used as event handlers. The migration effort may not be worth it if we eventually introduce a new component API that replaces classes.
. We really should have made this stable a while ago, as it’s clearly useful in synchronous mode. However, in asynchronous mode, it’s effectively a no-op, so it would be weird to ask everyone to migrate to a new API, only to remove…