Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[editorial] Compat: Move IDL for textureBindingViewDimension into the appropriate section #5056

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 30, 2025
Merged

[editorial] Compat: Move IDL for textureBindingViewDimension into the appropriate section #5056

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 14 additions & 9 deletions proposals/compatibility-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,11 @@ The primary goal of WebGPU Compatibility mode is to increase the reach of WebGPU

Since WebGPU Compatibility mode is a subset of WebGPU, all valid Compatibility mode applications are also valid WebGPU applications. Consequently, Compatibility mode applications will also run on user agents which do not support Compatibility mode. Such user agents will simply ignore the option requesting a Compatibility mode Adapter and return a Core WebGPU Adapter instead.

## WebGPU Spec Changes
# WebGPU Spec Changes

Spec changes are described in the following subsections.

## Initialization

When calling `GPU.requestAdapter()`, passing `featureLevel = "compatibility"` in the `GPURequestAdapterOptions` will indicate to the User Agent to select the Compatibility subset of WebGPU. Any Devices created from the resulting Adapter on supporting UAs will support only Compatibility mode. Calls to APIs unsupported by Compatibility mode will result in validation errors.

Expand All @@ -28,19 +32,12 @@ partial interface GPUAdapter {

As a convenience to the developer, the Adapter returned will have the `featureLevel` property set to `"compatibility"`.

```webidl
partial dictionary GPUTextureDescriptor {
GPUTextureViewDimension textureBindingViewDimension;
}
```

See "Texture view dimension may be specified", below.

## Compatibility mode restrictions

### 1. Texture view dimension may be specified

When specifying a texture, a `textureBindingViewDimension` property determines the views which can be bound from that texture for sampling (see "Proposed IDL changes", above). Binding a view of a different dimension for sampling than specified at texture creation time will cause a validation error. If `textureBindingViewDimension` is unspecified, use [the same algorithm as `createView()`](https://gpuweb.github.io/gpuweb/#abstract-opdef-resolving-gputextureviewdescriptor-defaults):

```
if desc.dimension is "1d":
set textureBindingViewDimension to "1d"
Expand All @@ -53,6 +50,14 @@ if desc.dimension is "3d":
set textureBindingViewDimension to "3d"
```

The WebIDL change:

```webidl
partial dictionary GPUTextureDescriptor {
GPUTextureViewDimension textureBindingViewDimension;
}
```

**Justification**: OpenGL ES 3.1 does not support texture views.

### 2. Color blending state may not differ between color attachments in a `GPUFragmentState`.
Expand Down
Loading