Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMore aggressively remove Fragment RestyleDamage #9008
Merged
Conversation
highfive
commented
Dec 17, 2015
|
|
|
@pcwalton r? |
|
|
Now clean up damage on all fragments that belong to a Flow. This ensures that damage does not re-propagate up to the parent Flow from the Fragments. It also means that the flow tree dump should show a more accurate picture of the state of the flow tree.
|
@bors-servo: r+ |
|
|
bors-servo
added a commit
that referenced
this pull request
Jan 8, 2016
More aggressively remove Fragment RestyleDamage Now clean up damage on all fragments that belong to a Flow. This ensures that damage does not re-propagate up to the parent Flow from the Fragments. It also means that the flow tree dump should show a more accurate picture of the state of the flow tree. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9008) <!-- Reviewable:end -->
|
|
|
@bors-servo retry |
bors-servo
added a commit
that referenced
this pull request
Jan 9, 2016
More aggressively remove Fragment RestyleDamage Now clean up damage on all fragments that belong to a Flow. This ensures that damage does not re-propagate up to the parent Flow from the Fragments. It also means that the flow tree dump should show a more accurate picture of the state of the flow tree. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9008) <!-- Reviewable:end -->
|
|
|
@bors-servo retry |
bors-servo
added a commit
that referenced
this pull request
Jan 9, 2016
More aggressively remove Fragment RestyleDamage Now clean up damage on all fragments that belong to a Flow. This ensures that damage does not re-propagate up to the parent Flow from the Fragments. It also means that the flow tree dump should show a more accurate picture of the state of the flow tree. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9008) <!-- Reviewable:end -->
|
|
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.
mrobinson commentedDec 17, 2015
Now clean up damage on all fragments that belong to a Flow. This ensures
that damage does not re-propagate up to the parent Flow from the
Fragments. It also means that the flow tree dump should show a more
accurate picture of the state of the flow tree.