# Qt 6.6.1 WebAssembly Error. WebGL: INVALID\_ENUM: bindFramebuffer: invalid target

**URL:** <https://community.khronos.org/t/qt-6-6-1-webassembly-error-webgl-invalid-enum-bindframebuffer-invalid-target/110398>\
**Category:** WebGL\
**Created:** [December 30, 2023, 12:07am UTC](https://community.khronos.org/t/qt-6-6-1-webassembly-error-webgl-invalid-enum-bindframebuffer-invalid-target/110398 "2023-12-30T00:07:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Dark\_Photon](https://community.khronos.org/user_avatar/community.khronos.org/dark_photon/32/4349_2.png) [@Dark\_Photon](https://community.khronos.org/u/Dark_Photon)\
**Post date:** [December 30, 2023, 1:28am UTC](https://community.khronos.org/t/qt-6-6-1-webassembly-error-webgl-invalid-enum-bindframebuffer-invalid-target/110398/3 "2023-12-30T01:28:21Z")

</div>

Docs show that `glBindFramebuffer()` only takes `GL_FRAMEBUFFER` in WebAssembly…

> **[WebGLRenderingContext: bindFramebuffer() method - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/bindFramebuffer)**
>
> The WebGLRenderingContext.bindFramebuffer() method of the
> WebGL API binds to the specified target the provided WebGLFramebuffer, or, if the framebuffer argument is null, the default WebGLFramebuffer, which is associated with the canvas rendering...

in WebGL 1 ([WebGLRenderingContext](https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext), which provides OpenGL ES 2.0).

WebGL 2 ([WebGL2RenderingContext](https://developer.mozilla.org/en-US/docs/Web/API/WebGL2RenderingContext)) provides OpenGL ES 3.0 rendering context, which supports `GL_DRAW_FRAMEBUFFER` and `GL_READ_FRAMEBUFFER` as well.

UPDATE: I guess that’s WebGL, not WebAssembly. But I suspect there may be something similar going on (OpenGL ES 2.0 vs. 3.0).

---

_[View the full topic](https://community.khronos.org/t/qt-6-6-1-webassembly-error-webgl-invalid-enum-bindframebuffer-invalid-target/110398)._