Expose limits on the adapter #489
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
There's no reason to leave this out anymore. Implementations can implement it whenever they want.
kvark
approved these changes
Nov 7, 2019
Kangz
approved these changes
Nov 7, 2019
kdashg
approved these changes
Nov 11, 2019
|
Resolution from the 2019-11-11 meeting: merge. |
litherum
added a commit
that referenced
this pull request
Nov 11, 2019
|
Is it possible to re-open a pull request after it's been reverted? |
|
During the call today there was some internal miscommunication. We’d like one more week to discuss this change internally. |
|
(I reverted this after emailing the mailing list and asking if it was okay. A representative from the company that wrote and merged this patch said it was okay.) |
kainino0x
added a commit
to kainino0x/gpuweb
that referenced
this pull request
Sep 23, 2020
This allows apps to receive information about individual available adapter limits, which which let the UA track privacy budgeting with better granularity. See also gpuweb#489, gpuweb#495; gpuweb#1098.
kainino0x
added a commit
to kainino0x/gpuweb
that referenced
this pull request
Sep 23, 2020
This allows apps to request information about individual available adapter limits, which lets the UA track privacy budgeting with better granularity. See also gpuweb#489, gpuweb#495; gpuweb#1098.
kainino0x
added a commit
to kainino0x/gpuweb
that referenced
this pull request
Oct 1, 2020
This allows apps to request information about individual available adapter limits, which lets the UA track privacy budgeting with better granularity. See also gpuweb#489, gpuweb#495; gpuweb#1098.
kainino0x
added a commit
to kainino0x/gpuweb
that referenced
this pull request
Oct 1, 2020
This allows apps to request information about individual available adapter limits, which lets the UA track privacy budgeting with better granularity. See also gpuweb#489, gpuweb#495; gpuweb#1098.
kainino0x
added a commit
to kainino0x/gpuweb
that referenced
this pull request
Dec 3, 2020
kainino0x
added a commit
to kainino0x/gpuweb
that referenced
this pull request
Dec 3, 2020
Merged
kainino0x
added a commit
that referenced
this pull request
Dec 15, 2020
I think it's been determined that this API shouldn't consider privacy budgeting in it's design. - UAs can still lazily-decide on GPULimits values. - UAs can still do bucketing ahead of time, or even based on queries to GPULimits members. - Apps can attempt requestDevice without checking limits, if they just want to know if their requested limits are supported. Exact IDL interface is TBD, but editorial. Needs more text to be filled out later. Also adds some other TODOs. See also #489, #495; #1098, #1100.
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.
There's no reason to leave this out anymore.
Implementations can implement it whenever they want.
Preview | Diff