Skip to content
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

Allow either bad-size=>INVALID_OP or bad-stride=>INVALID_VAL for vert… #3269

Merged

Conversation

kdashg
Copy link
Contributor

@kdashg kdashg commented Apr 1, 2021

…exAttribPointer.

Bad size is specified as INVALID_OPERATION here:
https://www.khronos.org/registry/webgl/specs/latest/1.0/#5.14.10

Too-large stride is specified as INVALID_VALUE here:
https://www.khronos.org/registry/webgl/specs/latest/1.0/#6.13

Copy link
Member

@kenrussell kenrussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay reviewing; had to revisit all the associated specs.

Just to clarify my understanding, is the problem with this particular test that both the size and stride are illegal, so it's ambiguous which one's validation causes the error (and the error differs depending on which one failed validation)?

@kdashg
Copy link
Contributor Author

kdashg commented Apr 6, 2021

That's right, though even this subtest's stated goal is to test too-large stride, which we spec'd in webgl to be INVALID_VALUE.

@kenrussell
Copy link
Member

I see - thanks for clarifying. Had a hard time finding again the too-large stride spec. Adjusted your message above to point to the two spec sections. Merging now.

@kenrussell kenrussell merged commit 9ac6bba into KhronosGroup:master Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants