27939 2015-01-31 20:25:35 +0000 Omissions from the VTTCue interface in the API 2015-02-01 02:41:29 +0000 1 1 1 Unclassified TextTracks CG WebVTT unspecified All All RESOLVED WORKSFORME http://dev.w3.org/html5/webvtt/ P2 normal --- 1 brinkje dave.null philipj self silviapfeiffer1 public-texttracks oldest_to_newest 117644 0 brinkje 2015-01-31 20:25:35 +0000 It seems to me that attributes for "id", "startTime", and "endTime" should be added to the VTTCue interface in section 7.1 of the January 2015 draft. The last two are parameters in the constructor. The identifier "id" is described elsewhere in the document and the attribute "id" is already allowed by several browsers. "id" could also be added as an optional parameter in the constructor. As a convenience to programmers using the VTTCue interface in applications, it would be useful to have way (possibly a function) for adding a WebVTT cue settings list to the cue as a single string using the same format that one would use in the WebVTT file on the start and end times lines. This string could also possibly be added as an optional parameter for the constructor. 117645 1 self 2015-01-31 21:14:40 +0000 VTTCue extends TextTrackCue: > interface VTTCue : TextTrackCue Which is defined here: https://html.spec.whatwg.org/#texttrackcue interface TextTrackCue : EventTarget { readonly attribute TextTrack? track; attribute DOMString id; attribute double startTime; attribute double endTime; attribute boolean pauseOnExit; attribute EventHandler onenter; attribute EventHandler onexit; }; So id, startTime and endTime are already part of it. 117647 2 silviapfeiffer1 2015-02-01 02:41:29 +0000 As Brendan explained in comment#1, VTTCue extends TextTrackCue, so all the attributes that you're missing are actually there.