This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The meaning of the cue settings is not explicitly spelled out - people have to infer it from the way in which they get used once mapped into HTML through <track> rather than being able to understand from reading the WebVTT spec. It would be nice to have an explanation where cue settings are first mentioned, near http://www.whatwg.org/specs/web-apps/current-work/webvtt.html#webvtt-cue-settings . Something like: A WebVTT vertical text cue setting: The vertical text cue setting defines whether text inside the text rendering box is rendered horizonally or vertically and whether it is ltr or rtl within the text rendering box. A WebVTT line position cue setting: The line position cue setting defines whether the text rendering box is positioned at the bottom of the video viewport or moved up from there by a viewport height percentage or number of lines. A WebVTT text position cue setting: The text position cue setting defines whether the text rendering box is positioned at the left of the video viewport or moved across from there by a viewport width percentage or number of pixels. A WebVTT size cue setting: The size cue setting defines the text size of text inside the text rendering box either in percent or pixels. A WebVTT alignment cue setting: The alignment cue setting defines whether the text inside the text rendering box is aligned to the box's start/middle/end, where start/middle/end is also influenced by the vertical cue setting, i.e. meaning top and bottom for vertically rendered text.
(In reply to comment #0) > The meaning of the cue settings is not explicitly spelled out - people have to > infer it from the way in which they get used once mapped into HTML through > <track> rather than being able to understand from reading the WebVTT spec. > > It would be nice to have an explanation where cue settings are first mentioned, > near > http://www.whatwg.org/specs/web-apps/current-work/webvtt.html#webvtt-cue-settings > . > > Something like: > > A WebVTT vertical text cue setting: > The vertical text cue setting defines whether text inside the text rendering > box is rendered horizonally or vertically and whether it is ltr or rtl within > the text rendering box. > > A WebVTT line position cue setting: > The line position cue setting defines whether the text rendering box is > positioned at the bottom of the video viewport or moved up from there by a > viewport height percentage or number of lines. > > A WebVTT text position cue setting: > The text position cue setting defines whether the text rendering box is > positioned at the left of the video viewport or moved across from there by a > viewport width percentage or number of pixels. > > A WebVTT size cue setting: > The size cue setting defines the text size of text inside the text rendering > box either in percent or pixels. > > A WebVTT alignment cue setting: > The alignment cue setting defines whether the text inside the text rendering > box is aligned to the box's start/middle/end, where start/middle/end is also > influenced by the vertical cue setting, i.e. meaning top and bottom for > vertically rendered text. Actually, much of this is explained at http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html#text-track-cue, but just not extracted into the WebVTT document.
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 r6366. Check-in comment: More information for cue syntax. http://html5.org/tools/web-apps-tracker?from=6365&to=6366
Thanks :-)