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
As of #34, when DeferredMountWithCallback is used, all deferred rendering is paused until that callback is invoked.
To avoid blocking all rendering, we might want to place the callback in a second queue for notifying when all rendering is complete, but avoid blocking the start of render of the next component. This should be optional, so that we can also block when waiting for render to be completed before starting the next.
This change does not break API.
We should introduce a new property for signalling when we explicitly want to block further rendering, it could look something like this:
As of #34, when
DeferredMountWithCallback
is used, all deferred rendering is paused until that callback is invoked.To avoid blocking all rendering, we might want to place the callback in a second queue for notifying when all rendering is complete, but avoid blocking the start of render of the next component. This should be optional, so that we can also block when waiting for render to be completed before starting the next.
This change does not break API.
We should introduce a new property for signalling when we explicitly want to block further rendering, it could look something like this:
The text was updated successfully, but these errors were encountered: