28857 2015-06-26 17:21:30 +0000 [MSE] Support attachment (and inspection) of MediaSource to HTMLMediaElement via HTMLMediaElement.srcObject 2015-10-13 23:16:38 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified PC Linux RESOLVED MOVED P2 normal --- 1 wolenetz wolenetz ddorwin jdsmith mike Paul.Cotton public-html-media watsonm public-html-bugzilla oldest_to_newest 121489 0 wolenetz 2015-06-26 17:21:30 +0000 A long time ago, there was some discussion [1] and a bug [2] about supporting srcObject (and deprecating createObjectURL) usage for MSE. Since HTML 5.1 appears to now include HTMLME.srcObject [3], and MSE has not yet reached Proposed Rec. stage, the time seems ripe to both: 1) Implement srcObject per HTML 5.1 in HTMLMediaElement 2) Deprecate usage in MSE spec of createObjectURL() as mechanism for attaching MediaSource to HTMLMediaElement, in favor of new spec text mentioning srcObject as the preferred mechanism. MSE attachment (and retrieval via) srcObject, among other possible benefits, would allow extension-free debugging using Chrome devtools (for example) of MSE players. Currently, there's no "easy" way of getting the MediaSource object in a devtools session to debug it. Simply $('video').srcObject would be cool :) [1] https://lists.w3.org/Archives/Public/public-html-media/2013Nov/0004.html [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23775 [3] http://www.w3.org/html/wg/drafts/html/master/semantics.html#dom-media-srcobject 121490 1 wolenetz 2015-06-26 17:27:05 +0000 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? 123701 2 wolenetz 2015-10-13 23:16:38 +0000 This bug has been migrated to the GitHub issue tracker. Please follow/update progress using the GitHub issue: https://github.com/w3c/media-source/issues/28 Paul/Jerry/Mark: Please see the information requested in https://www.w3.org/Bugs/Public/show_bug.cgi?id=28857#c1 and reply on the GitHub issue.