From 0cc0346bbb9628c94d093949f0a6b279e67f16f2 Mon Sep 17 00:00:00 2001 From: Jake Archibald Date: Tue, 11 Jul 2017 13:26:30 +0100 Subject: [PATCH] Clarifying use of codecs & metadata when making ranged requests --- source | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/source b/source index bdbcf7c69ce..fbdf006500c 100644 --- a/source +++ b/source @@ -33017,11 +33017,15 @@ interface HTMLMediaElement : HTMLElement {

The user agent may go on to use whatever means necessary to fetch the resource (within the constraints put forward by this and other specifications); for example, reconnecting to - the server in the face of network errors, using the ranged fetch steps to - perform HTTP range retrieval requests for a given start and end range, or switching to a - streaming protocol. The user agent must consider a resource erroneous only if it has given - up trying to fetch it.

+ the server in the face of network errors, or switching to a streaming protocol. The user + agent must consider a resource erroneous only if it has given up trying to fetch it.

+ +

The user agent may use the ranged fetch + steps to perform HTTP range retrieval requests for a given start and (optional) end + range. Through its knowledge of container formats, the user agent may issue a ranged request + to gather metadata it knows to be at the end of the resource. Or, if the media is seeked, + the browser may use metadata to convert a temporal range to a byte range and make a ranged + request.

To determine the format of the media resource, the user agent must use the rules for sniffing audio and video specifically.