Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fiber] Handle Bailed Out HostText update and MultiChildText test #8371

Merged
merged 1 commit into from
Nov 29, 2016

Conversation

sebmarkbage
Copy link
Collaborator

This handles the case where a host text bails out. In that case we need to reuse its previous memoizedProps. We should also only schedule an actual update if it did actually change its text content.

I updated the unit test to ignore comment nodes if we're using Fiber.

When combined with #8331 the test actually passes.

This handles the case where a host text bails out. In that case we need to
reuse its previous memoizedProps. We should also only schedule an actual
update if it did actually change its text content.

I updated the unit test to ignore comment nodes if we're using Fiber.
@sebmarkbage sebmarkbage merged commit f634b81 into facebook:master Nov 29, 2016
acusti pushed a commit to brandcast/react that referenced this pull request Mar 15, 2017
)

This handles the case where a host text bails out. In that case we need to
reuse its previous memoizedProps. We should also only schedule an actual
update if it did actually change its text content.

I updated the unit test to ignore comment nodes if we're using Fiber.
laurinenas pushed a commit to laurinenas/react that referenced this pull request May 28, 2018
)

This handles the case where a host text bails out. In that case we need to
reuse its previous memoizedProps. We should also only schedule an actual
update if it did actually change its text content.

I updated the unit test to ignore comment nodes if we're using Fiber.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants