Kai Ninomiya

> and already set tonemapping to `extended` `GPUCanvasConfiguration`'s `toneMapping: { mode: 'extended' }` is a canvas output option and doesn't affect anything else on the device, so it has nothing...

To continue the [meeting discussion](https://docs.google.com/document/d/1fDwRkfnhAsQW6XMJwCC1pFf3Vp7-Jzkqz_EvD2lAs88/edit?usp=sharing) @mwyrzykowski: I don't think the choice of default is affected at all by what the display is going to do. Defaulting to infinity doesn't make...

That's true, I was thinking canvas couldn't have infinite headroom but if the pixel format is f16 then it could (and the canvas proposals specifically mention this). As for my...

That's correct. You would need to load into `rgba16float`, and then render into an `rgba16float` canvas configured with `toneMapping: { mode: "extended" }`, *that* will make the browser will handle...

I don't think it is viable for external textures to default to HDR. For example, a straightforward 360 video player that uses `importExternalTexture` (many of which surely already exist) can...

> We would need to create a table listing every single pixel format, and what the expected behavior is. We didn't list `"rgba16unorm"`, `"rgba32uint"`, etc. Those need answers, too. We...

Any canvas-output headroom should look fine on all displays, as the browser would tonemap the canvas's headroom to the display's headroom if they don't match. (The app might just be...

> In particular, it is defined behaviour to set a position to NaN from the vertex shader -> that results in the primitive culling. Does it also work to set...

They're there as guards to make sure people don't use them accidentally. Technically not deprecated, just never intended to be used in the first place, we could remove the `@deprecated`...

The Vulkan spec section is here: https://registry.khronos.org/vulkan/specs/1.3/html/chap24.html#vertexpostproc-clipping 0 ≤ zc ≤ wc which looks like ours, though it's hard to figure out the definitions of these variables. Actually, I think...