Recognize valid IDL buffer source primitive types #18003
Closed
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
foolip
reviewed
Jul 25, 2019
lukebjerring
force-pushed
the
buffersource
branch
from
cf337b7
to
faf4d75
Compare
|
Closing this as redundant; seems to have no meaningful effect on the results. |
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.
Buffer source types defined here:
https://heycam.github.io/webidl/#idl-buffer-source-types
These types are never explicitly mentioned in IDL, so will not be pulled in as dependencies. As a result, we see
Unrecognized type Uint8ClampedArrayand similar when these types are referenced.This PR simply recognizes those types and makes a simple typeof x === 'object' assertion.