W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

[Bug 13359] <track> A way is needed to identify the type of data in a track element

From: <bugzilla@jessica.w3.org>
Date: Fri, 07 Sep 2012 23:13:08 +0000
Message-Id: <E1TA7jY-0003fx-O7@jessica.w3.org>
To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13359

--- Comment #65 from Bob Lund <b.lund@cablelabs.com> 2012-09-07 23:13:03 UTC ---
(In reply to comment #64)
> (In reply to comment #61)
> > (In reply to comment #59)
> > > Wouldn't the page know what the format was? After all, it was the one that gave
> > > the URL.
> > 
> > I assume this is a reply t o comment #56.
> > 
> > In the case where the URL is specified in the video element, the page author
> > would need to use different versions of the JS dispatch function depending on
> > the media type of the content pointed to by the URL. Will the author always be
> > able to make this association?
> 
> Since it's the author providing the URL, he should know the media type of the
> content behind the URL. Can you explain a situation where that wouldn't be the
> case?
> 
> > What about in a dynamically created page where
> > the only piece of information about the content is the URL?
> 
> Even then the page author is the one writing the JS, so they would know.

If all the page generator (human author or otherwise) has is the URL to the
content then how will it know the type of content?

> 
> > Also, wouldn't this be a source of errors? The metadata available to the page
> > author might be wrong, saying that a piece of content is Ogg when in fact it is
> > WebM. A UA that supports both will play the content but the wrong dispatch
> > function will be used.
> 
> If the author doesn't know the media type/can't find out through probing, why
> would the browser get it right?

The browser has access to the content-type when it tries to play the content,
right?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 7 September 2012 23:13:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 7 September 2012 23:13:10 GMT