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
Make renderbufferStorageMultisample with DEPTH_STENCIL and samples>0 generate INVALID_OPERATION. #3031
Make renderbufferStorageMultisample with DEPTH_STENCIL and samples>0 generate INVALID_OPERATION. #3031
Conversation
The other option is to make |
This is a resolution for #2902. |
My preference would be to reject the unsized DEPTH_STENCIL enum with samples > 0 with INVALID_OPERATION. Would you please consider updating the test to assert that instead? We'll be happy to change Chrome's implementation to generate INVALID_OPERATION instead of INVALID_ENUM to follow. CC @jdarpinian @shrekshao for any thoughts. |
Sure! |
…generate INVALID_OPERATION.
86c53f2
to
6f63c89
Compare
PTAL! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM per discussion above.
@jdarpinian @shrekshao heads up that we need to file a bug about changing this validation in Chrome because this test will start failing during the next conformance roll. |
WebGL2 does not allow allocating multisample renderbuffers with the GL_DEPTH_STENCIL format but Chrome has been generating the wrong error since the WebGL test was updated in KhronosGroup/WebGL#3031. TBR=kbr@chromium.org Bug: chromium:1082455 Bug: angleproject:5227 Change-Id: Ia9818968578a47023958c35c9b037e8907f76091 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498111 Reviewed-by: Geoff Lang <geofflang@chromium.org> Reviewed-by: James Darpinian <jdarpinian@chromium.org> Commit-Queue: Geoff Lang <geofflang@chromium.org> Cr-Commit-Position: refs/heads/master@{#822304}
WebGL2 does not allow allocating multisample renderbuffers with the GL_DEPTH_STENCIL format but Chrome has been generating the wrong error since the WebGL test was updated in KhronosGroup/WebGL#3031. TBR=kbr@chromium.org Bug: chromium:1082455 Bug: angleproject:5227 Change-Id: Ia9818968578a47023958c35c9b037e8907f76091 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498111 Reviewed-by: Geoff Lang <geofflang@chromium.org> Reviewed-by: James Darpinian <jdarpinian@chromium.org> Commit-Queue: Geoff Lang <geofflang@chromium.org> Cr-Commit-Position: refs/heads/master@{#822304} GitOrigin-RevId: bd3558e3a9fd6f96c938a47f5467d9b765c641d4
Firefox allows DEPTH_STENCIL with samples >= 0.
Chrome allows samples==0, but INVALID_ENUM for samples >= 1.