This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#webvtt-cue-text-dom-construction-rules Complete: http://www.whatwg.org/c#webvtt-cue-text-dom-construction-rules Comment: The WebVTT timestamp seconds separator is always a full stop Posted from: 83.218.67.122 by philipj@opera.com User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.186 Version/12.00
ProcessingInstruction node whose target is "timestamp" and whose data is a WebVTT timestamp representing the value of the WebVTT Timestamp Object, with all optional components included and with the seconds separator being a U+002E FULL STOP character (.). The last part appears to be left-over from when either a comma or a full stop was allowed as the separator. Now only full stop is allowed: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#webvtt-timestamp
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r6675. Check-in comment: vestigial text http://html5.org/tools/web-apps-tracker?from=6674&to=6675