Add AbortError or EncodingError exception as argument for rejected flush() promises #188
Labels
breaking
Interface changes that would break current usage (producing errors or undesired behavior).
Alligns with how promises are rejected in the ImageDecoder proposal (#152)
Saying why the promise was rejected seems helpful. Not strictly necessary, since they may know why via other means (e.g. EncodingError would also be fired via the error callback).
The text was updated successfully, but these errors were encountered: