14338 2011-09-30 08:08:28 +0000 <track> What does line position auto actually do? 2011-10-26 23:01:40 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#text-track-cue-automatic-line-position P3 blocker --- 1 contributor ian annevk eric.carlson ian mike philipj public-html-admin public-html-wg-issue-tracking silviapfeiffer1 public-html-bugzilla oldest_to_newest 57546 0 contributor 2011-09-30 08:08:28 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#text-track-cue-automatic-line-position Complete: http://www.whatwg.org/c#text-track-cue-automatic-line-position Comment: <track> What does line position auto actually do? 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.205 Version/12.00 57547 1 philipj 2011-09-30 08:10:41 +0000 "A line position: Either a number giving the position of the lines of the cue, to be interpreted as defined by the writing direction and snap-to-lines flag of the cue, or the special value auto, which means the position is to depend on the other active tracks." What should auto actually do here? Is it equivalent to -1, or is it completely UA-defined? If so, why? 57638 2 ian 2011-10-02 16:37:58 +0000 It's all defined in the rendering section. 57691 3 philipj 2011-10-03 08:23:35 +0000 We can't find anything about "auto" and "line position" in http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#webvtt-cue-text-rendering-rules 57692 4 annevk 2011-10-03 08:31:23 +0000 I can see line position referenced several times, but the algorithm does not seem to account for the "auto" value. E.g. it has let top be y-position followed by vw, which would not work for auto. 57734 5 ian 2011-10-03 23:41:44 +0000 Yeah, wow. That's weird. I wonder how I missed that. The DOM attribute for it also seems to be wrong (it gives a positive line number instead of a negative one). I think I should fix this by introduce a new term "text track cue computed line position" which has the same value as the line position, unless it's auto, in which case it determines its value automatically, in the same way that the DOM attribute does now, except with a negated line number. Then, use that term in the rendering, and to define the DOM attribute. 59014 6 ian 2011-10-26 23:00:29 +0000 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: see comment 5 59015 7 contributor 2011-10-26 23:01:40 +0000 Checked in as WHATWG revision r6769. Check-in comment: Somehow the automatic feature of cue line position was never properly specified. http://html5.org/tools/web-apps-tracker?from=6768&to=6769