[Bug 21627] texttrackcue API change

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

--- Comment #3 from Glenn Adams <glenn@skynav.com> ---
First, the term "deprecated" does not apply since we are still not in REC
state. If an external organization references a not yet complete (i.e., not yet
REC) W3C specification, then they must take the risk of having that spec change
before arriving at REC.

Second, as I mention, the fielded implementations are effectively experimental,
and as Sylvia indicates, little impact is expected by reworking the TTC
constructor signature.

Third, this is the purpose of having a CR period, otherwise known as "Call for
Implementations", in which experience can be gathered and fed back to the spec
process. It is a general understanding that this process may end up producing
changes in the spec.

Fourth, it is well recognized that the VTT specification material in HTML5 was
due to be moved to another specification, and that what remained behind should
be sufficiently generic to accommodate different text track content types.

So what Sylvia is suggesting is already well understood and consistent with
expectations.

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

Received on Tuesday, 9 April 2013 16:13:34 UTC