This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Created attachment 1033 [details] compare "start" to "left" alignment needs The currently allowed alignment values of <track> and WebVTT cues are "start", "end" and "middle". These make sense when you just regard multi-line text rendering for a certain area and want the text to be aligned based on its directionality. However, where text is left (or right) aligned along the shape of a person or other object or underneath a person, we actually need the value "left" (and "right"), since a simple translation of the cues should not need to change the cue settings. See the attached image for an example.
So, I propose to add the values "left" and "right" to the set of allowed alignment values in <track> and WebVTT cues.
Since WebVTT is now (relatively officially) part of a CG, I would instead suggest that all references to it be removed from the W3C HTML5 specification until such time as it reaches an acceptable level of status.
(In reply to comment #2) > Since WebVTT is now (relatively officially) part of a CG, I would instead > suggest that all references to it be removed from the W3C HTML5 specification > until such time as it reaches an acceptable level of status. There are two locations where specs need to change: one and most importantly in the HTML spec where it concerns the <track> element. I mentioned the consequences on WebVTT for completeness and because both specs have the same editor.
Interesting use case.
This involves changes to HTML.
This bug was cloned to create bug 17973 as part of operation convergence.
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-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/7d448cfdf1fc5981594a9b85637991e5e4cdde88 Rationale: accepted WHATWG change