- From: <bugzilla@jessica.w3.org>
- Date: Thu, 07 Oct 2010 05:14:27 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10320 --- Comment #15 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2010-10-07 05:14:27 UTC --- (In reply to comment #7) > (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.) Video players increasingly use a rudimentary or full HTML parser. We probably want to exclude <script> support though. > * 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? It was a suggestion. > * Things like <img> in cues will either behave erratically, or require complex > logic to load them ahead of time. I expect the browser to do what it always does: when it comes across a <img> element, it loads the resource in a best effort. If it doesn't load in time, it stops loading it (just like when you navigate away from a page that is mid-loading). -- 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, 7 October 2010 05:14:29 UTC