Closed takahirox closed 4 years ago
I guess the problem is from that the extension doesn't implement properly this behavior?
The buffers attached to an opaque framebuffer MUST be cleared to the values in the table below when first created, or prior to the processing of each XR animation frame. This is identical to the behavior of the WebGL context’s default framebuffer.
How to reproduce the problem
The examples seems to work correctly on the realy Samsung S8+ Chrome canary so I speculate this is a WebXR emulator extension side bug.