Add datapoints for optional depthCompare and depthWriteEnabled properties

[chrisdavidmills]

Summary

In Chrome 120, the depthCompare and depthWriteEnabled properties of the createRenderPipeline/createRenderPipelineAsync descriptors have been made optional when not needed. See https://developer.chrome.com/blog/new-in-webgpu-120#changes_to_depth-stencil_state.

See gpuweb/gpuweb#4318 for spec change.

This PR adds a datapoint for this, for each method.

Test results and supporting details

Related issues

Project issue: mdn/content#36370

[beaufortfrancois]

LGTM with nits

[beaufortfrancois]

Ditto

[chrisdavidmills]

Ooop, I've only got one comment from you, which says "Ditto". I'm assuming there's one missing.

[chrisdavidmills]

@beaufortfrancois ^

[beaufortfrancois]

Yes. I was wondering why "notes": "Currently supported on ChromeOS, macOS, and Windows only." was not present for both.

[chrisdavidmills]

TBH, they should be added to all datapoints and sub-data points. Added in last commit.

[caugner]

@chrisdavidmills If this is based on a spec change (I assume it is?), can you please link the spec PR in the description? 🙏

Otherwise it's hard for me as a reviewer to check the description and validate the standard_track: true part.

PS: I checked both the content issue and the Chrome blog post, and they don't seem to link there.

[chrisdavidmills]

@chrisdavidmills If this is based on a spec change (I assume it is?), can you please link the spec PR in the description? 🙏

Otherwise it's hard for me as a reviewer to check the description and validate the standard_track: true part.

PS: I checked both the content issue and the Chrome blog post, and they don't seem to link there.

Added. For future reference, you can generally find the spec change links in the "dawn" issues, for example at https://developer.chrome.com/blog/new-in-webgpu-120#changes_to_depth-stencil_state, where it says "See issue dawn:2132".