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

[Bug 13943] <track> The "bad cue" handling is stricter than it should be

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Sep 2011 08:27:25 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R8pUD-0007Jc-KZ@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13943

--- Comment #14 from Philip Jägenstedt <philipj@opera.com> 2011-09-28 08:27:22 UTC ---
(In reply to comment #12)
> How many lines do you want to parse before expecting a line with "-->" in it?
> This has the potential danger that if somebody really screwed up their WEBVTT
> file and it's a very long file that we end up parsing the whole file before we
> notice that there aren't any cues. Is that desirable?

The current parser only ever aborts parsing in the header, never while parsing
cues, so this is already the case. (Step 31 looks like it might, but it can
only happen at EOS.) I think this is very much desirable, as the alternative is
to either die on the first error or have an arbitrary limit for how many
non-cue lines we tolerate before dying.

-- 
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 Wednesday, 28 September 2011 08:27:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:19 UTC