[worklets] Add language for non-determinism in a note.#472
Open
bfgeek wants to merge 4 commits into
Open
Conversation
Member
|
Some thoughts on how to test this. Could the spec have a limit to say that the same scope cannot be used more than n times in a row, where n is a large number? Then the implementation could be to randomly pick a scope and randomly switch, but a test that checks that it does eventually switch would both be supported by what the spec says, and would pass in a reasonable time frame. |
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
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.
This adds a note that user-agents must introduce some non-determinism into the selection process for a paint worklet global scope.
This came up in blinks intent-to-ship thread:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Jex3idOld48
Issue: #471