Html.ReactWithInit improvements #858
Merged
Conversation
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
dustinsoftware
force-pushed
the
delayed-init
branch
from
fb2d9d8 to
71d68a7
Compare
This was referenced Jul 5, 2019
Closed
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.
Happy 4th! This addresses a year-old bug report in #543
If you wanted to use output caching, it wasn't really feasible to use
Html.ReactWithInitwithout introducing a render performance penalty, because your script tags had to all be added to the top of the page. This PR waits for theDOMContentLoadedevent so that won't be an issue anymore. Calls toHtml.Reactare unaffected.