- From: <bugzilla@jessica.w3.org>
- Date: Fri, 26 Jun 2015 17:27:05 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28857
Matt Wolenetz <wolenetz@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Paul.Cotton@microsoft.com,
| |watsonm@netflix.com
Flags| |needinfo?(watsonm@netflix.c
| |om),
| |needinfo?(Paul.Cotton@micro
| |soft.com),
| |needinfo?(jdsmith@microsoft
| |.com)
--- Comment #1 from Matt Wolenetz <wolenetz@google.com> ---
philipj@opera.com also provided some indication of how the spec update might be
accomplished:
"The HTML spec to target when implementing srcObject is
https://html.spec.whatwg.org/#dom-media-srcobject. It would be nice if
http://w3c.github.io/media-source/ could simply refer to the latest versions of
all of its references, including the File API. You can see in
https://github.com/w3c/webvtt/ how I arranged things to have different
references for different versions of the WebVTT spec."
Paul/Jerry/Mark: would adding .srcObject support be something that would change
the API so much to require a re-entry into CR process for the MSE spec? If not,
would including deprecation of the
HTMLME.src=createObjectURL(mediaSourceObject) MSE attachment mechanism trigger
the need for the re-entry into CR process?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 26 June 2015 17:27:12 UTC