14929 2011-11-25 08:40:30 +0000 <track> use the same names in the DOM API as in WebVTT's cue settings 2012-07-18 18:48:03 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#dom-texttrackcue-direction P3 critical Unsorted 14646 1 contributor ian fs ian mike silviapfeiffer1 zcorpan contributor oldest_to_newest 60469 0 contributor 2011-11-25 08:40:30 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#dom-texttrackcue-direction Complete: http://www.whatwg.org/c#dom-texttrackcue-direction Comment: <track> use the same names in the DOM API as in WebVTT's cue settings Posted from: 85.227.157.105 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.942.0 Safari/535.8 60470 1 zcorpan 2011-11-25 08:44:22 +0000 (In reply to http://www.w3.org/Bugs/Public/show_bug.cgi?id=14646#c7) > Fair enough. > > D: will become vertical: and the values will be changed to lr and rl > L: will become line: > T: will become position: > S: will become size: > A: will become align: This sounds good. However, I would like the settings and their exposure in the DOM API to be aligned, so that it's more obvious what things are called (compare with content attributes and IDL attributes in HTML). For instance, vertical: is "direction":"horizontal" | "vertical" | "vertical-lr" in the DOM API. It would be better if it were "vertical":"" | "rl" | "lr". 60472 2 zcorpan 2011-11-25 08:53:04 +0000 snapToLines and the magical value "auto" are also a bit annoying, though I'm not sure what to do about them. 61165 3 ian 2011-12-07 23:27:25 +0000 Yeah, I should examine what to do here. Unfortunately this blocks the other bug on an HTML spec change. 64449 4 ian 2012-02-22 20:04:33 +0000 Ok, .alignment => .align is obvious low-hanging fruit, so let's definitely do that. Looking at the others... 64451 5 contributor 2012-02-22 20:05:08 +0000 Checked in as WHATWG revision r7006. Check-in comment: rename TextTrackCue.alignment to .align to match the setting name in VTT. http://html5.org/tools/web-apps-tracker?from=7005&to=7006 64453 6 ian 2012-02-22 20:07:18 +0000 I liked linePosition and textPosition, but I guess calling them 'line' and 'position' isn't so bad. It's better than changing VTT to use 'line-position:' and 'text-position:', I guess. And "text position" isn't any less ambiguous than "position" anyway. 64454 7 contributor 2012-02-22 20:08:26 +0000 Checked in as WHATWG revision r7007. Check-in comment: rename TextTrackCue.linePosition and .textPosition to .line and .position respectively to match the setting names in VTT. http://html5.org/tools/web-apps-tracker?from=7006&to=7007 64456 8 ian 2012-02-22 20:10:30 +0000 Having .vertical return "" for horizontal direction is a bit weird, but I guess it's ok too, since it means you can do if (cue.vertical) { /* vertical */ } else { /* horizontal */ } ...and yet get its exact value to work out what kind of vertical. 64457 9 contributor 2012-02-22 20:12:04 +0000 Checked in as WHATWG revision r7008. Check-in comment: rename TextTrackCue.direction to .vertical (and change the values accordingly) to match the setting names in VTT. http://html5.org/tools/web-apps-tracker?from=7007&to=7008