#4275 (comment) mentioned that "snorm10-10-10-2" vertex format is missing due to D3D12 not having it natively.

However:

• Metal does have snorm10-10-10-2: https://developer.apple.com/documentation/metal/mtlvertexformat/int1010102normalized?language=objc
• Vulkan does have snorm10-10-10-2: https://docs.vulkan.org/spec/latest/chapters/formats.html#VkFormat
• there is an OpenGL ES 2.0 based extension: https://registry.khronos.org/OpenGL/extensions/OES/OES_vertex_type_10_10_10_2.txt (for WebGPU compatibility mode profiles)
• so could the browsers easily polyfill the missing D3D12 support?

I was implementing my own decoding to do x*2-1, and while doing so felt a bit like it would fit well for the browser to do this?

Presumably some GPUs might have this support natively, so e.g. on mobile Vulkan devices, a native support for "snorm10-10-10-2" might be a tiny bit more optimal for performance?

Assuming the browser papering over D3D12 quirks could be easy, this could help ergonomy of the API for users? (and if D3D13 Ultimate Ultimate adds the functionality in the future, it would be a transparent optimization to existing site content)