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/complete/the-iframe-element.html Multipage: http://www.whatwg.org/C#dom-texttrackcue-alignment Complete: http://www.whatwg.org/c#dom-texttrackcue-alignment Comment: <track> should be clearer about which strings cue.alignment returns Posted from: 88.131.66.80 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.21 Safari/535.2
Chipping in here, I've recently had some thoughts on the alignment values of WebVTT which 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, I've been seeing examples were text was right aligned along the shape of a person or other object because it made sense to be aligned there, independent of the directionality of the text. So, my suggestion is to add "right" and "left" to the alignment values of WebVTT, too.
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 r6615. Check-in comment: This was poorly defined, to say the least. http://html5.org/tools/web-apps-tracker?from=6614&to=6615