28465 2015-04-10 23:34:29 +0000 MSE does not work with Mixed Content, unlike video/audio.src= 2015-10-13 23:06:45 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified PC All RESOLVED MOVED P2 normal --- 27239 1 wolenetz wolenetz b.lund ddorwin jdsmith mike public-html-media watsonm public-html-bugzilla oldest_to_newest 119434 0 wolenetz 2015-04-10 23:34:29 +0000 Mixed Content (https://w3c.github.io/webappsec/specs/mixedcontent/) provides a mechanism for secure origins to load audio/video/source content from insecure origins as optionally-blockable content (though the user agent, the document settings, or the user could block the load, and the user agent should indicate that mixed content is present). However, the same insecure origin content does not work with secure origin MSE because it is treated as blocked content. This bug tracks aligning MSE with the existing Mixed Content behavior for video.src=. 119435 1 wolenetz 2015-04-10 23:40:41 +0000 A current proposal for allowing MSE to work with mixed content is described in https://lists.w3.org/Archives/Public/public-html-media/2015Apr/0013.html. Roughly, the proposal depends on: Streams API defining an opaque Stream with properties [described in the proposal] . Fetch implementing support for opaque Responses [described in the proposal] Fetch exposing Streams, including opaque ones, from the Response object. Mixed Content spec including opaque Responses and/or Streams as appropriate. 119436 2 watsonm 2015-04-10 23:46:24 +0000 Whilst I don't have any particular objections to this, I'd note that no one responded to the original proposal to indicate that they would find this useful. 123695 3 wolenetz 2015-10-13 23:06:45 +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/22