W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10320] Allow an arbitrary string as the voice for forwards compatilbity

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 12:54:35 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P1Ieh-0006tv-QY@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10320

--- Comment #7 from Philip Jägenstedt <philipj@opera.com> 2010-09-30 12:54:35 UTC ---
(In reply to comment #6)
> I think we should address forward compat by using the HTML fragment parsing
> algorithm and using the class attribute for "voices".

What about these issues with using an HTML parser:

* Non-browser user agents are likely not going to be happy to include an HTML
parser and ECMAScript engine for something as simple as subtitles. (Assuming
the fragment parser executes <script>, something I assume but haven't checked.)

* 1 document per cue is likely significant memory overhead. Is 1 document per
cue actually necessary, or just something that was suggested at some point?

* Things like <img> in cues will either behave erratically, or require complex
logic to load them ahead of time.

* class="philip" and class="henri" doesn't carry the semantics that there are
two different speakers, which would be necessary to allow the user (not author)
to style different speakers differently.

-- 
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 Thursday, 30 September 2010 12:54:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC