- From: Anne van Kesteren <annevk@opera.com>
- Date: Tue, 16 Jun 2009 17:32:13 +0200
- To: "Jamie Lokier" <jamie@shareable.org>, "Simon Pieters" <simonp@opera.com>
- Cc: "Ian Hickson" <ian@hixie.ch>, "Robert O'Callahan" <robert@ocallahan.org>, "Adam Barth" <w3c@adambarth.com>, "Larry Masinter" <masinter@adobe.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, public-html@w3.org
On Tue, 16 Jun 2009 17:25:43 +0200, Jamie Lokier <jamie@shareable.org> wrote: > Simon Pieters wrote: >> On Fri, 12 Jun 2009 20:55:29 +0200, Ian Hickson <ian@hixie.ch> wrote: >>> I've updated HTML5 to require that Content-Types of types that are not >>> supported cause the resource to be ignored (even if it would otherwise >>> be supported). >> >> If a UA does not know what is not supported, is it reasonable to >> consider anything that is not video/* or audio/* to be not supported? > > For video, content negotiation is probably going to end up being done > in Javascript rather than HTTP, or by User-Agent recognition. Still, if the user agent does a request, should it abort the request if the media type of the response is not video/* or audio/*? -- Anne van Kesteren http://annevankesteren.nl/
Received on Tuesday, 16 June 2009 15:33:10 UTC