Editorial review: Document size requirement changes for GPUBuffers mapped at creation

[chrisdavidmills]

Description

In Chrome 138, the size requirements for GPUBuffers mapped at creation have changed. During a GPUDevice.createBuffer() call, if mappedAtCreation is set true and size is not a multiple of 4, a RangeError exception is thrown.

See https://developer.chrome.com/blog/new-in-webgpu-138#size_requirement_changes_for_buffers_mapped_at_creation.

This PR adds a mention of the change. cc @beaufortfrancois.

Question — if the RangeError is thrown, will an invalid GPUBuffer object still be returned? If not, should I remove the corresponding entry from the validation section?

Motivation

Additional details

Related issues and pull requests

[github-actions]

Preview URLs

• /en-US/docs/Web/API/GPUDevice/createBuffer

(comment last updated: 2025-10-17 13:15:54)

[beaufortfrancois]

Question — if the RangeError is thrown, will an invalid GPUBuffer object still be returned? If not, should I remove the corresponding entry from the validation section?

When RangeError is thrown, there's no GPUBuffer returned. Yes, you should remove the corresponding entry from the validation section.

[beaufortfrancois]

LGTM with comments

[chrisdavidmills]

Question — if the RangeError is thrown, will an invalid GPUBuffer object still be returned? If not, should I remove the corresponding entry from the validation section?

When RangeError is thrown, there's no GPUBuffer returned. Yes, you should remove the corresponding entry from the validation section.

Ah ha, thought so ;-)

[pepelsbey]

Looks good! Thank you :)