Bug 1846102 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
We need to distinguish the concept of a "supported" codec string from a "valid" codec string to meet the latest spec validating the codec [here](https://github.com/w3c/webcodecs/pull/707). In short, the "invalid" is more like "empty" rather than "unrecognized". The codec string "theora" is valid even if WebCodec does't support it.
Revision 1 by
on 
We need to distinguish the concept of a "supported" codec string from a "valid" codec string to meet the latest spec validating the codec [here](https://github.com/w3c/webcodecs/pull/707). In short, the "invalid" is more like "empty" rather than "unrecognized". The "recognized" string must be a "valid" string, while the "valid" string may be "unrecognized". A "recognized" codec may not be "supported". That is, "valid" codec strings set ⊇ "recognized" codec strings set ⊇ "supported" codec strings set.

For example, the codec string "theora" is valid even if WebCodec does't support it.
Revision 2 by
on 
We need to distinguish the concept of a "supported" codec string from a "valid" codec string to meet the latest spec validating the codec [here](https://github.com/w3c/webcodecs/pull/707) (bug 1843974). In short, the "invalid" is more like "empty" rather than "unrecognized". The "recognized" string must be a "valid" string, while the "valid" string may be "unrecognized". A "recognized" codec may not be "supported". That is, "valid" codec strings set ⊇ "recognized" codec strings set ⊇ "supported" codec strings set.

For example, the codec string "theora" is valid even if WebCodec does't support it.
Revision 3 by
on 
We need to distinguish the concept of a "supported" codec string from a "valid" codec string to meet the latest spec validating the codec [here](https://github.com/w3c/webcodecs/pull/707) (bug 1843974). In short, the "invalid" is more like "empty" rather than "unrecognized". The "recognized" string must be a "valid" string, while the "valid" string may be "unrecognized". A "recognized" codec may not be "supported". That is, "valid" codec strings set ⊇ "recognized" codec strings set ⊇ "supported" codec strings set.

For example, the codec string "theora" is valid but WebCodec does't support it.
Revision 4 by
on 
We need to distinguish the concept of a "supported" codec string from a "valid" codec string to meet the latest spec validating the codec [here](https://github.com/w3c/webcodecs/pull/707) (bug 1843974). In short, the "invalid" is more like "empty" rather than "unrecognized". The "recognized" string must be a "valid" string, while the "valid" string may be "unrecognized". A "recognized" codec may not be "supported". That is, "valid" codec strings set ⊇ "recognized" codec strings set ⊇ "supported" codec strings set.

For example, the codec string "theora" is "valid" but it's "unsupported" in WebCodecs.

Back to Bug 1846102 Comment 0