Client transitions still need to render in order#962
Merged
Conversation
During client transitions the root structure is built up using a state machine that requires an in-order render. First render can still go out of order because the server has already laid out the root structure. This fixes redfin#961.
gigabo
commented
Oct 11, 2017
| @@ -601,26 +601,35 @@ class ClientController extends EventEmitter { | |||
| } | |||
Contributor
Author
There was a problem hiding this comment.
May be easier to look at with whitespace changes hidden.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
During client transitions the root structure is built up using a state machine that requires an in-order render. First render can still go out of order because the server has already laid out the root structure.
This fixes #961.