demo · v136

Compat mode comparison

Request the WebGPU device with requiredFeatures: ["core-features-and-limits"] and compare its limits side-by-side with a default device. The new feature is the spec's way of telling implementations: this is the floor, refuse to instantiate if the adapter doesn't reach it. Useful for libraries that target only conforming hardware.

Probing WebGPU adapter…

default request

features:

limits:

required: ["core-features-and-limits"]

features:

limits:

the code

const adapter = await navigator.gpu.requestAdapter();
const device  = await adapter.requestDevice({
  requiredFeatures: ["core-features-and-limits"],   // 136+
});
// On a sub-core adapter this requestDevice rejects, exiting the library
// before it tries any baseline-assumed operation.

why this angle

The sibling concept reads what an adapter supports. This concept demonstrates the use: gate requestDevice on the new feature so that libraries can assume the baseline. Without the feature flag they'd have to enumerate limits and bail out themselves — ugly, error-prone, and split across every wrapper.

see also