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 19:41:35 +0000
Message-Id: <E1TA4Qp-0000RU-OZ@jessica.w3.org>
To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13359

--- Comment #64 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2012-09-07 19:41:31 UTC ---
(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.

> 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?

-- 
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 19:41:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 7 September 2012 19:41:37 GMT