[Bug 21627] texttrackcue API change

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

--- Comment #2 from xham <graham.clift@am.sony.com> ---
(In reply to comment #1)
> I don't see an impact on interoperability coming from DLNA (I assume that is
> the standards organization you refer to).
> 
Whether this spec is in use by DLNA or not is up to standards organization that
is using it to reveal not me.

> It is simply too early in the process for this to be an issue. In
> particular, there are no devices deployed yet using this developing
> standard, and there are no web pages serving content being transmitted to
> such hypothetical devices.

 There is a problem when a standards organization references and uses the API
from HTML5.0 but the latest WebKit and Mozilla builds start to use the APIs
from HTML5.1. It means creating a fork in implementations/updates to these
devices and as well as putting API detection into the content that uses these
APIs. If none of these APIs are in use then why not change the HTML5.0 spec now
to have compatibility with the future standard? Or why not have the
functionality remain in the TextTrackCue and have the WebVTTCue simply add to
it as needed?

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

Received on Tuesday, 9 April 2013 15:52:38 UTC