E405 Issues in "validating GPUDepthStencilState" algorithm · Issue #4508 · gpuweb/gpuweb · GitHub
[go: up one dir, main page]
Skip to content

Issues in "validating GPUDepthStencilState" algorithm #4508

New issue
New issue
Open
Open
Issues in "validating GPUDepthStencilState" algorithm#4508
Labels
apiWebGPU APIcopyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.)
Milestone
Milestone 2
@Kangz

Description

@Kangz
Kangz
opened on Mar 8, 2024

The above phrasing states that if depthCompare != "always", then format must have a depth component.

Now that depthCompare is optional, should that be interpreted as if depthCompare != undefined && depthCompare != "always", then format must have a depth component?

I.e. what should happen if I don't fill in depthCompare, or I fill in .depthCompare = undefined;? It seems like the above rules are saying that in that case the format should have a depth component, which might be a bit odd?

Originally posted by @juj in #4318 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    apiWebGPU APIcopyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.)

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      0