This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25948 - [WebVTT] The parser should not set the region to null when e.g. size != 100
Summary: [WebVTT] The parser should not set the region to null when e.g. size != 100
Alias: None
Product: TextTracks CG
Classification: Unclassified
Component: WebVTT (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: Web Media Text Tracks CG
Depends on:
Reported: 2014-06-02 14:03 UTC by Philip Jägenstedt
Modified: 2014-06-09 21:35 UTC (History)
2 users (show)

See Also:


Description Philip Jägenstedt 2014-06-02 14:03:22 UTC
"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.
Comment 1 Silvia Pfeiffer 2014-06-02 22:29:17 UTC
makes sense
Comment 2 Philip Jägenstedt 2014-06-04 13:53:24 UTC
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.
Comment 3 Philip Jägenstedt 2014-06-04 14:16:51 UTC
Comment 4 Silvia Pfeiffer 2014-06-09 13:21:01 UTC
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.
Comment 5 Philip Jägenstedt 2014-06-09 21:35:14 UTC
The spec has been updated and I've filed