`GPUQueue.writeBuffer` size argument inconsistent with web API

[justin-cotarla]

Version: Deno 2.5.6

According to MDN:

[size] is a number of elements if data is a TypedArray, and a number of bytes if not. If omitted, size will be equal to the overall size of data, minus dataOffset.

When passing a Float32Array to writebuffer however, Deno does not interpret the it to be a TypedArray and therefore expects size to be a number of bytes and not a number of elements in the array.

This is inconsistent with what would happen if the same code were run in the Node or Browser contexts.

As far as I can tell this isn’t an intentional design feature, I don’t see any mention of this in the docs.

[Hajime-san]

https://gpuweb.github.io/gpuweb/#dom-gpuqueue-writebuffer

Size of content to write from data to buffer. Given in elements if data is a TypedArray and bytes otherwise.

I think that you pointing out is right.
The size argument should be ignored when data is a TypedArray.

deno/ext/webgpu/queue.rs

Lines 103 to 116 in 58f7435

	fn write_buffer(
	&self,
	#[webidl] buffer: Ref<GPUBuffer>,
	#[webidl(options(enforce_range = true))] buffer_offset: u64,
	#[anybuffer] buf: &[u8],
	#[webidl(default = 0, options(enforce_range = true))] data_offset: u64,
	#[webidl(options(enforce_range = true))] size: Option<u64>,
	) {
	let data = match size {
	Some(size) => {
	&buf[(data_offset as usize)..((data_offset + size) as usize)]
	}
	None => &buf[(data_offset as usize)..],
	};

Is this a good first issue?