Skip to content

Reporting DeviceLost in various functions and callbacks #209

@kainino0x

Description

@kainino0x

Currently we report DeviceLost in the following places aside from just the DeviceLost callback - places where the JS API does not report it:

The JS API specifies generally that async operations pretend to work successfully after the device is lost (except for MapAsync): gpuweb/gpuweb#1629 (comment)

Should we keep these DeviceLost enum values or should we do more like what the JS API does and pretend everything worked? Notably WASM can only do what JS does, so this makes it a native-only return value - but so are many of the others.

Metadata

Metadata

Assignees

No one assigned

    Labels

    asyncAsynchronous operations and callbackserrorsError reportinghas resolutionIssue is resolved, just needs to be done

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions