- From: Victor Carbune <victor.carbune@gmail.com>
- Date: Fri, 2 Mar 2012 17:06:20 +0200
- To: Philip Jägenstedt <philipj@opera.com>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Simon Pieters <simonp@opera.com>, public-texttracks@w3.org
Hello, >> I don't mind changing the parser here, BTW. > Me neither, obviously. I'm also supporting a modification of the parser here. I'm concerned about particular unnatural situations that should be handled the same by browsers. Here's one that comes to my mind (maybe there are others as well): Let's say such a cue (startTime < endTime) is a missed cue - skipped during playback through monotic increase. According to the spec, when the cue is processed, both enterEvent and exitEvent need to be dispatched (in ascending order of the time associated with them). Depending on the implementation, various situations can appear: * Without extra processing, exitEvent gets fired before enterEvent * Dispatching enterEvent associated with endTime and exitEvent with startTime doesn't sound natural * Not dispatching events at all in such a situation is not reglemented by the spec. Victor
Received on Friday, 2 March 2012 15:07:12 UTC