Implement bufferData(target, size, usage) support in WebGL bindings

[Copilot]

Fixes the missing implementation of bufferData(target, size, usage) in the WebGL JavaScript bindings. This method was already supported in the underlying C++ implementation (client_graphics::WebGLContext::bufferData) but the JavaScript binding layer was throwing an error instead of calling the appropriate C++ method.

Problem

The WebGL binding in src/bindings/webgl/rendering_context-inl.hpp contained a TODO comment and explicitly threw an error when bufferData() was called with a number as the second parameter:

// This would fail with "bufferData(target, size, usage) is not supported yet."
gl.bufferData(gl.ARRAY_BUFFER, 1024, gl.STATIC_DRAW);

Solution

Removed the artificial limitation and implemented proper handling for the size-based bufferData call:

• Extract target and usage parameters upfront
• Check if the second parameter is a number (size)
• If so, call the existing C++ method: glContext_->bufferData(target, size, usage)
• Preserve all existing functionality for data-based calls (TypedArray, DataView, ArrayBuffer)

Testing

Added comprehensive test fixture fixtures/html/webgl-conformance/bufferdata-size-test.html that validates:

• Basic buffer allocation with size
• Different buffer targets (ARRAY_BUFFER, ELEMENT_ARRAY_BUFFER)
• Different usage patterns (STATIC_DRAW, DYNAMIC_DRAW, STREAM_DRAW)
• Large buffer allocation
• Backward compatibility with existing TypedArray-based calls

Changes

• Modified: src/bindings/webgl/rendering_context-inl.hpp (net -3 lines)
• Added: Test fixture for validation
• No breaking changes: All existing bufferData usage continues to work

This change enables WebGL applications to efficiently allocate GPU buffers with specific sizes without providing initial data, which is a common pattern for dynamic buffer usage.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• registry.npmmirror.com
  • Triggering command: npm ci (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.