v0.1.16415 Aug 2026·Rendering, JavaScript & JIT

WebGL textures + control-flow on the GPU

The WebGL-on-GPU path grows to the two shapes almost every real shader needs: textures and control flow. A sampler2D uniform now runs on the device - the bound texture is uploaded to a wgpu texture, texture2D() becomes textureSampleLevel against a real texture + sampler bind group, and the wrap and filter modes match the software sampler exactly. And a fragment shader with local variables and a for/while loop (with break and continue) now translates to WGSL and draws on the GPU instead of falling back. Both are readback-proven against the software rasteriser: the textured quad is bit-exact (max_diff=0), and the loop-and-local triangle matches within a single level per channel (only anti-aliased edges differ). It stays an accelerator, never a correctness risk: a shader the translator still cannot express - two or more distinct textures, user-defined functions, an uninitialised local, a non-bool condition - declines to the proven software path, so nothing renders wrong. The GPU aspect moves 48 to 49. The overall holds at 57.

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 3 changes

Rendering	WebGL textures on the GPU: a sampler2D shader uploads its bound texture to a wgpu texture and samples it with textureSampleLevel through a texture + sampler bind group at @group(1); REPEAT / MIRRORED_REPEAT / CLAMP wrap and NEAREST / LINEAR filter map to the wgpu sampler, matching the software sampler bit-for-bit (max_diff=0).
JavaScript & JIT	WebGL control-flow shaders on the GPU: the GLSL->WGSL translator now emits local variable declarations and for / while loops with break and continue, inferring each local's type so WGSL's int/float rules hold (an int loop counter stays int) - the loop-and-local triangle renders on the device within one level of software (max_diff=1).
JavaScript & JIT	Still an accelerator, not a dependency: a shape the translator cannot yet express - two or more distinct samplers, a user-defined function, an uninitialised local, a non-bool loop/if condition - declines to None and keeps the proven software path, so an unsupported shader renders correctly rather than wrong; the whole engine gate holds at 6375 of 6375.