-
Notifications
You must be signed in to change notification settings - Fork 45
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
WGPUSurfaceGetCurrentTextureStatus needs a value for "surface not configured" #291
Comments
FWIW, because there is only one error case in JS, there will be only two possible return values in Wasm ( |
May 23 meeting (sorry for delay):
Note in #255 (comment) we decided to also use the same status for errors in struct chaining (for which we would normally use |
…ppens See webgpu-native/webgpu-headers#291 Bug: 42241264 Change-Id: Ia8669fe9838c98f86942af9adaf835fddaf36fa6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/192185 Commit-Queue: Corentin Wallez <[email protected]> Reviewed-by: Kai Ninomiya <[email protected]> Reviewed-by: Austin Eng <[email protected]>
Done in #319. |
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225 Fixes webgpu-native#64
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225 Fixes webgpu-native#64
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225 Fixes webgpu-native#64
There's just one error case in
getCurrentTexture()
in the JS spec:We don't have a
WGPUSurfaceGetCurrentTextureStatus
to represent this currently.Should we add a new one, or merge with one of those?
Followup issue to #203. cc @rajveermalviya @Kangz @eliemichel
The text was updated successfully, but these errors were encountered: