attribute USVString WebGLObject.label, application-provided.

[kdashg]

This is similar to WebGPU's GPUObjectBase.label.

[kdashg]

https://www.w3.org/TR/webgpu/#gpuobjectbase

interface mixin GPUObjectBase {
    attribute USVString label;
};

[greggman]

The difference between WebGPU's label and WebGL is that, AFAIK, WebGPU always returns an object. WebGL does not

// on lost context
const b = gl.createBuffer();
b.label = "verts";              // crash!, can't set property label of `null`

WebGPU doesn't have this issue

More in the spirit of WebGL would be gl.setLabel(obj?: WebGLObject, label: UVString) because then it could handle null.

Sure, the user can check for null though.

[kdashg]

I strongly prefer the ergonomics of .label, and would rather champion infallible allocations instead of reduced ergonomics.

[greggman]

In the spirit of the fact that WebGL is supposed to make porting OpenGLES code easier, isn't WEBGL_debug the more WebGL-ish thing to support?

Of course it's doesn't have to be either/or but still.

[kdashg]

I believe my proposal is the best way forward for the most users.

[kkinnunen-apple]

Looks good, thanks.

[kenrussell]

This direction sounds good. While it's a different API style than other WebGL extensions, it's expected that this would be implementable/supportable at the native level pretty much ubiquitously.