Media Capabilities allow for web sites to better determine what content to serve to the end user. Currently a media element offers the canPlayType method (https://html.spec.whatwg.org/multipage/media.html#dom-navigator-canplaytype-dev <https://html.spec.whatwg.org/multipage/media.html#dom-navigator-canplaytype-dev>) to determine if a container/codec can be used. But the answer is limited as a maybe/probably type answer.
It gives no ability to determine if a particular resolution can be played well/smoothly enough or be done in a power efficient manner (e.g. will it be hardware accelerated). This has been a particular problem with sites such as YouTube that serves VP9 under all circumstances even if the user agent won't play it well (VP9 is mostly done via software decoding and is CPU itensive). This has forced us to indiscriminately disable VP9 altogether). For YouTube to know that VP9 could be used for low resolution but not high-def ones would allow them to select the right codec from the start. This issue is tracked in bugzilla 1409664 (https://bugzilla.mozilla.org/show_bug.cgi?id=1409664 <https://bugzilla.mozilla.org/show_bug.cgi?id=1409664>) The proposed spec is available at https://wicg.github.io/media-capabilities/ <https://wicg.github.io/media-capabilities/> Chrome has shipped it a while ago now and talking to several partners (including YouTube, Netflix, Facebook etc) , Media Capabilities support has been the number one request. We intend to implement and ship this API very soon. Early comment and feedback will be welcome. Kinds regards Jean-Yves
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
