- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 26 Apr 2012 22:29:54 +1000
- To: Ian Hickson <ian@hixie.ch>
- Cc: public-texttracks@w3.org
On Thu, Apr 26, 2012 at 1:34 PM, Ian Hickson <ian@hixie.ch> wrote: > On Thu, 26 Apr 2012, Silvia Pfeiffer wrote: > >> >> It also makes it easier for cue editors to use the parser and API >> >> without having to worry about losing cues that happen to have >> >> incorrect timings. >> > >> > I don't see the value. If it's an invalid cue, then it's no different >> > than losing a cue that happens to have a syntax error. >> >> In fact, if we don't lose it, they may never notice their mistake, >> seeing as it ends up in the cue list structure. > > I'm not sure who "they" means here. A cue editor that wants to expose this > can trivially do so by just showing all cues with negative durations. I meant the WebVTT file authors with "they". I was mostly thinking about those that use a Web browser to author their files and look at what JavaScript lists for finding out whether their cues got parsed. A more intelligent editor should indeed expose the problems during authoring. Silvia.
Received on Thursday, 26 April 2012 12:30:49 UTC