XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] RE: Highly Declarative Designs

Hi David,

> Are you sure?

That is what the book [1] says (I was quoting from the book). Jeremy Keith is a pretty sharp fellow, so I assume it is correct.

/Roger

[1] The example comes from the book, "HTML5 for Web Designers" by Jeremy Keith.



-----Original Message-----
From: David Carlisle [mailto:davidc@nag.co.uk] 
Sent: Tuesday, February 08, 2011 8:27 AM
To: Costello, Roger L.
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] RE: Highly Declarative Designs

On 08/02/2011 13:01, Costello, Roger L. wrote:

>     <audio>
>         <source src="witchitalineman.ogg">
>         <source src="witchitalineman.mp3">
>     </audio>
>

> A browser that can play back Ogg Vorbis files will look no further
> than the first<source>  element. A browser that can play MP3 files
> but not Ogg Vorbis files will skip over the first<source>  element
> and play the file in the second<source>  element.


Are you sure?

I don't see anything in here:

http://www.whatwg.org/specs/web-apps/current-work/#concept-media-load-algorithm

to suggest that the browser will use the file extension in this case, 
rather than fetching the specified resouce and determining its file type 
by inspecting its content.

David


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS