- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Sat, 9 Oct 2010 01:20:28 +1300
On Fri, Oct 8, 2010 at 2:48 PM, Philip J?genstedt <philipj at opera.com> wrote: > Even if very few subtitles use inline SVG, SVG in <object>, <img>, > <iframe>, <video>, self-referencing <track>, etc in the cue text, all > implementations would have to support it in the same way for it to be > interoperable. That's quite an undertaking and I don't think it's really > worth it. > User agents only need to be interoperable over the common subset of HTML features they support. HTML is mostly designed to degrade gracefully when a user agent encounters elements it doesn't support. The simplest possible video player would use an HTML parser (hopefully off-the-shelf) to build some kind of DOM structure. Then it can group text into paragraphs for rendering, and ignore the rest of the content. In practice, we'll have to deal with user agents that support different sets of WebSRT features --- when version 2 of WebSRT is developed, if not before. Why not use existing, proven machinery --- HTML --- to cope with that situation? Rob -- "Now the Bereans were of more noble character than the Thessalonians, for they received the message with great eagerness and examined the Scriptures every day to see if what Paul said was true." [Acts 17:11] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101009/b60abe4f/attachment-0001.htm>
Received on Friday, 8 October 2010 05:20:28 UTC