[whatwg] WebSRT feedback
robert at ocallahan.org
Fri Oct 8 05:20:28 PDT 2010
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
"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...
More information about the whatwg