W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 13995] Don't check Content-Type for <track>

From: <bugzilla@jessica.w3.org>
Date: Fri, 21 Oct 2011 08:29:22 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RHATi-0004wt-U3@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13995

--- Comment #27 from Philip Jägenstedt <philipj@opera.com> 2011-10-21 08:29:19 UTC ---
(In reply to comment #25)
> What do you want to have happen if you browse a browser to a page that is
> labeled text/vtt and starts with "WEBVTT"?

Not relevant to this bug, but just displaying it as plain text would seem the
natural choice. I don't suppose we want to disallow fancier display methods,
automatic translation, etc, but that sounds unlikely to happen.

> What do you want to have happen if you browse a browser to a page that is
> labeled text/plain and starts with "WEBVTT"?

Per the "Web Pages" section in the sniffing spec text/plain leads to sniffing,
so it'll be sniffed as text/vtt and the same thing as above will happen.

> What do you want to have happen if a <track> points to a text/vtt file that
> starts with "WEBVTT"?

It'll be parsed and rendered as WebVTT.

> What do you want to have happen if a <track> points to a text/xml file that
> starts with "WEBVTT"?

Per comment 21, it will be sniffed as text/vtt and then parsed+rendered as
WebVTT. (The same will happen regardless of the media type.)

Finally, although you didn't ask, navigating to a text/xml file that starts
with "WEBVTT" would not cause it to be sniffed as WebVTT, since text/xml is not
in the table that leads to sniffing in step 2 of
<http://tools.ietf.org/html/draft-ietf-websec-mime-sniff-03#section-4>.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 21 October 2011 08:29:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:06 UTC