This is an idea that has been raised by some developers using WebGPU for a video effects pipeline. They have shaders that depending on the configuration of the processing graph take in a GPUExternalTexture for the binding (because it is the source video) or a GPUTextureView (because it is an intermediate node of the graph). It would be most convenient for them if a GPUTextureView with the right properties (float32-filterable, 2D, single subresource) could be used for an externalTexture binding.

In terms of implementation, this path should most likely trivial to support because aside from the change in createBindGroup, we expect that GPUExternalTexture should already support some form of RGBA data as some software videos will certainly use that.