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 upProperly track whether a new scene has been built to fix the debug indicator #3255
Conversation
…dicator.
|
The OSX taskcluster failure is unrelated. |
|
@bors-servo r+ |
|
|
bors-servo
added a commit
that referenced
this pull request
Oct 31, 2018
Properly track whether a new scene has been built to fix the debug indicator I broke the new scene indicator when when removing redundant frame builds. Now that we don't necessarily send a new frame to the renderer when the scene is built, the information is lost so we have store it somewhere. r? anyone Fixes #3247. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/3255) <!-- 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.
nical commentedOct 31, 2018
•
edited by larsbergstrom
I broke the new scene indicator when when removing redundant frame builds. Now that we don't necessarily send a new frame to the renderer when the scene is built, the information is lost so we have store it somewhere.
r? anyone
Fixes #3247.
This change is