Skip to main content
New Participant
December 17, 2025
Question

MetaQuest Browser Bug: INVALID_ENUM using XRProjectionLayer

This issue already got posted here: 

Steps to reproduce the problem

  1. Launch Meta Quest Browser (tested on v41.0) on a Meta Quest 3.
  2. Start WebXR session that initializes an XRProjectionLayer with:
    { textureType: "texture-array" }
  3. render loop: iterate through the views (without using OVR_multiview2 extension).
  4. For each view, attach the subImage.colorTexture to the framebuffer using gl.framebufferTextureLayer
  5. Call gl.clear(gl.COLOR_BUFFER_BIT)
  6. Call gl.getError()

I tried to bind the colorTexture from a subimage of a projection layer with textureType: "texture-array" via:
`gl.framebufferTextureLayer(gl.FRAMEBUFFER, gl.COLOR_ATTACHMENT0, subImage.colorTexture, 0, subImage.imageIndex);`

I seem to get a GL_INVALID_ENUM (1280) error on the first gl rendering operation (only for the first eye/left) when checking for errors. This does not happen if the subimage texture is of type: textureType: "texture"

Is this a bug in the Meta Quest Browser Chromium fork?