[Bug 21851] revert removal of text and getCueAsHTML members; address constructor changes

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21851

--- Comment #29 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
(In reply to comment #28)
> (In reply to comment #27)
> 
> > The main reason I didn't introduce an UnprasedCue object is that I don't
> > really see the advantage of creating a basically empty object, just to get a
> > constructor:
> > 
> > [Constructor(double startTime, double endTime, DOMString text)]
> > interface UnparsedCue : TextTrackCue {
> > };
> 
> You would also add the text property to UnparsedCue, since it doesn't need
> to be on TextTrackCue, right?

Could do... but...

Then we need to make VTTCue a child of UnparsedCue, too, right?

And then I don't see a need for the original TextTrackCue object any more,
because all cues that get created for all the use cases that we currently cover
will have some textual content being part of it, so would get created as an
UnparsedCue.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 12 August 2013 13:18:36 UTC