- From: wolenetz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jan 2020 21:23:10 +0000
- To: public-html-media@w3.org
wolenetz has just created a new issue for https://github.com/w3c/media-source: == Consider restricting isTypeSupported to fail if unexpected parameters is included == Example: "webm/audio;codecs=opus;test='6'": Should isTypeSupported() return true for this on an implementation that supports opus in WebM with MSE? Or should the extra parameter/value ";test='6'" cause failure? The bytestream format specs, especially ISOBMFF, refer to various RFCs that allow other parameters (like profile) and codec encodings (like rfc2231), though implementations tend to ignore unrecognized parameters today. Should they fail instead in vNext? Please view or discuss this issue at https://github.com/w3c/media-source/issues/247 using your GitHub account
Received on Tuesday, 14 January 2020 21:23:12 UTC