[v3] fix identification of sealed tags during streaming #1997
Conversation
This file contains 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
The "sealed" concept was on the stylesheet level, when it should have actually been on a per-tag basis. By moving the sealed status down, we can now accurately tell when a tag has been flushed to the client and is no longer eligible for style injection.
quantizor
changed the title
kitten
approved these changes
Sep 10, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The "sealed" concept was on the stylesheet level, when it should
have actually been on a per-tag basis. By moving the sealed status
down, we can now accurately tell when a tag has been flushed to the
client and is no longer eligible for style injection.
Same as #1996 but for v3