Re: Unifying regions and non-regions layout algorithms

On Fri, Nov 22, 2013 at 2:04 AM, David Singer <singer@apple.com> wrote:
>
> On Nov 21, 2013, at 14:54 , Philip Jägenstedt <philipj@opera.com> wrote:
>
>> So, I have been to FOMS, and there was a lot of talk about WebVTT.
>>
>> One of the things we discussed was how to integrate WebVTT Regions
>> more deeply into the spec, to not make it look like something bolted
>> on to the side. The different layout algorithms for the regions and
>> non-regions cases is a key component here.
>
> Bother
>
> certainly, I tried to make suggestions that matched the overall idea that layout (as previously defined) happened within a ‘region’ which, by default, was the entire area assigned to the VTT, and that all the regions bolt-on did was define smaller sub-spaces in which the same layout occurred.  Did we fail?

See http://dev.w3.org/html5/webvtt/#rendering

At step 12 there is a branch, with one path for the regions case and
one path for the non-regions case. What I'm saying that we should try
to weave these paths together as much as possible, ideally so that the
only thing that the presence of a region does is to constrain the
available space for layout.

Philip

Received on Friday, 22 November 2013 10:37:56 UTC