Custom error types

[Djuffin]

Currently WebCodecs rely on DOMExceptions with different names, but DOMException names are deprecated .
For proper and granular error reporting WebCodecs might need a special error type, like WebGpu pipeline error.

We might also need a special error type for rejecting promises and reporting errors via VideoEncoder and VideoDecoder callbacks.

[chrisn]

Looking at the list of DOMException names it's only IndexSizeError, InvalidAccessError, TypeMismatchError, and URLMismatchError that are marked as deprecated. The WebCodecs spec doesn't use any of those so I think we're OK in that regard.

[aboba]

Can we use EncodingError to indicate an issue with the data provided to the Encoder/Decoder, and something else (e.g. OperationError) to indicate a resource issue (e.g. hardware encoder resource no longer available),

[xingri]

@Djuffin, @aboba If it is possible, can I get a reference on the current working in progress?
Would like to investigate any possible changes on application side.

[chrisn]

Discussed in Media WG meeting, 30 May 2023, minutes.

[xingri]

Discussed in Media WG meeting, 30 May 2023, minutes.

Thanks @chrisn for the update.