25948 2014-06-02 14:03:22 +0000 [WebVTT] The parser should not set the region to null when e.g. size != 100 2014-06-09 21:35:14 +0000 1 1 1 Unclassified TextTracks CG WebVTT unspecified PC All RESOLVED FIXED P2 normal --- 1 philipj dave.null philipj silviapfeiffer1 public-texttracks oldest_to_newest 107128 0 philipj 2014-06-02 14:03:22 +0000 "If cue's text track cue line position is not text track cue automatic line position or cue's text track cue size is not 100 or cue's text track cue writing direction is not horizontal, let cue's text track cue region be null." "This makes sure that no matter in which order the cue settings are provided, if if the cue has a text track cue line position or a text track cue size setting or is text track cue vertical growing left or growing right writing direction, the text track cue region will be ignored." This should be part of the rendering algorithm, since scripts can change the properties later to violate the invariant that this tries to preserve. To the extent possible, providing the settings to the parser or with a script should do the same thing. 107160 1 silviapfeiffer1 2014-06-02 22:29:17 +0000 makes sense 107273 2 philipj 2014-06-04 13:53:24 +0000 Hmm, trying to actually move this, I'm thinking it's better to just get rid of the logic. If one has specified both a region and something that is ignored in regions then one of them is going to be ignored and it doesn't seem to matter much which it is. The simplest way is to just use the region if it's set. 107274 3 philipj 2014-06-04 14:16:51 +0000 https://github.com/w3c/webvtt/pull/88 107523 4 silviapfeiffer1 2014-06-09 13:21:01 +0000 Need to think through the consequences, though. Do vertical regions still behave correctly? Is there some text in the region specification parts that was not thought through to potentially be vertical rather than horizontal? Either leave this bug open or add a new one to remind us. 107550 5 philipj 2014-06-09 21:35:14 +0000 The spec has been updated and I've filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=26023