W3C home > Mailing lists > Public > public-html-admin@w3.org > April 2013

[Bug 21627] New: texttrackcue API change

From: <bugzilla@jessica.w3.org>
Date: Mon, 08 Apr 2013 15:31:19 +0000
To: public-html-admin@w3.org
Message-ID: <bug-21627-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21627

            Bug ID: 21627
           Summary: texttrackcue API change
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: graham.clift@am.sony.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

The API for TexttTrackCue from the HTML5 specification
http://www.w3.org/TR/html5/embedded-content-0.html#texttrackcue

is a superset of the APIs in the latest HTML5.1 specification:
http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#texttrackcue

where the differences, including the constructor, seem to be captured in a new
WebVTTCue api
http://dev.w3.org/html5/webvtt/#webvttcue

It seems that part of the TextTrackCue object is being deprecated already and
this could have an impact on interoperability. I work in a standards
organization that will be heavily relying upon this API. Could you help me
understand why this action has been taken? 

It seems it could have been possible to keep the constructor on the
TextTrackCue object and overload the methods needed for the new WebVTTCue API

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 8 April 2013 15:31:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:33 UTC