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

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

--- Comment #31 from Philip Jägenstedt <philipj@opera.com> ---
As far as I am concerned, there are two questions of interest:

1. Should TextTrackCue have the .text property?

2. Should there be a TextTrackCue constructor?

For the first question, I don't really see why it should. Even for TTML it
doesn't seem like a useful property to have, even if the DOM fragment
representing the cue can be serialized. It seems far more useful to just expose
the DOM fragment directly, no? I'm not sure if anyone has serious plans to
support bitmap subtitles in things like MPEG-2, but a text property obviously
wouldn't make sense for that either.

If there's no text property there's nothing much useful you can do with a
TextTrackCue object, so why bother with a constructor?

(Most of the discussion for these changes happened while I was on leave, so let
me know if I've missed something.)

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

Received on Monday, 12 August 2013 14:11:43 UTC