You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experimenting on the components branch (b1f1f7a) and found that the webgl context behaves different on a 'canvas Element' then on a 'canvas Instance'.
Consider the following testcase:
<application>
<meta>
<id>com.nidium.github.issues.XX</id>
<viewport>640x360</viewport>
</meta>
<layout>
<canvasid="3dcanvas" ></canvas>
</layout>
<script>
const let_it_crash = false;
if (let_it_crash) {
var canvas3d = document.getElementById("3dcanvas");
} else {
/*
* this gives
[ERROR:CanvasContext] (CanvasContext.cpp:472) fbo fatal error 8cd6
*/
var canvas3d = new Canvas(640, 360);
document.canvas.add(canvas3d);
}
var gl = canvas3d.getContext("webgl");
</script>
</application>
The text was updated successfully, but these errors were encountered:
Ah yes indeed, I already experimented a similar issue while testing WebGL on the component branch.
There is currently a bug on the master branch that prevents WebGL from working (the android merge + commit f516273). Once WebGL are fixed, I'll investigate into this one.
I am experimenting on the components branch (b1f1f7a) and found that the webgl context behaves different on a 'canvas Element' then on a 'canvas Instance'.
Consider the following testcase:
The text was updated successfully, but these errors were encountered: