-
Notifications
You must be signed in to change notification settings - Fork 23
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
Remove STOPPING state handling #78
Merged
Merged
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
@bors-servo r+ |
📌 Commit 1376366 has been approved by |
bors-servo
pushed a commit
that referenced
this pull request
Nov 1, 2019
Remove STOPPING state handling STOPPING is the transition into the IDLE state, not an exit event Ideally we should be using this for triggering visibility blurred events, but I'm never seeing the IDLE or VISIBLE states. I suspect this has something to do with wait_for_animation_frame, HL may be pausing w_a_f when it goes into IDLE, and throwing away the events we don't immediately ask for. I suspect those events are going into EventsLost, whch we don't yet check. r? @jdm
💔 Test failed - checks-travis |
@bors-servo r=jdm |
📌 Commit 867137f has been approved by |
bors-servo
pushed a commit
that referenced
this pull request
Nov 8, 2019
Remove STOPPING state handling STOPPING is the transition into the IDLE state, not an exit event Ideally we should be using this for triggering visibility blurred events, but I'm never seeing the IDLE or VISIBLE states. I suspect this has something to do with wait_for_animation_frame, HL may be pausing w_a_f when it goes into IDLE, and throwing away the events we don't immediately ask for. I suspect those events are going into EventsLost, whch we don't yet check. r? @jdm
☀️ Test successful - checks-travis |
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.
STOPPING is the transition into the IDLE state, not an exit event
Ideally we should be using this for triggering visibility blurred events, but I'm never seeing the IDLE or VISIBLE states.
I suspect this has something to do with wait_for_animation_frame, HL may be pausing w_a_f when it goes into IDLE, and throwing away the events we don't immediately ask for.
I suspect those events are going into EventsLost, whch we don't yet check.
r? @jdm