Re: IE Blog Posting on HLS and DASH Type 1 support

This is great news! I would also like to hear the answers to Aarons questions.

And a further question would be whether there will be any callback mechanism for unrecognized tags in the manifests (e.g. “X-“ tags in m3u8)?

Joe

> On Jan 30, 2015, at 10:10 AM, Aaron Colwell <acolwell@google.com> wrote:
> 
> Hi Jerry,
> 
> Congrats. I've got a few questions though:
> 1. Do all the URLs inside the manifests go through CORS verification?
> 2. What is mixed-content & tainting behavior if the manifests and/or content URLs don't have the same origin or are a mix of http & https content?
> 
> It would be good to get these behaviors specified in the HTML spec since the current text seems to implicitly assume that the URL passed to .src is the only URL that needs to be considered for media playback. The media URLs in DASH & HLS manifests kind of violate that assumption. It would be nice to get concensus on the appropriate behavior so everyone implements the same thing and it is consistent with current web platform security best practices.
> 
> Aaron
> 
> On Thu Jan 29 2015 at 5:25:52 PM Jerry Smith (WINDOWS) <jdsmith@microsoft.com <mailto:jdsmith@microsoft.com>> wrote:
> Just a quick note.  Microsoft has been working to implement HLS and DASH Type 1 streaming on top of MSE.  We posted some information on this today on the IE Blog:  http://blogs.msdn.com/b/ie/archive/2015/01/29/simplified-adaptive-video-streaming-announcing-support-for-hls-and-dash-in-windows-10.aspx <http://blogs.msdn.com/b/ie/archive/2015/01/29/simplified-adaptive-video-streaming-announcing-support-for-hls-and-dash-in-windows-10.aspx>
> 
> 
> Let me know if you have any feedback.
> 
> 
> 
> Jerry
>