Re: Absolute region positioning (was Re: Alternative approach to scrolling, with demos)

Thanks. That helps. Any ideas for how we can begin to get a look at the
visual impact of proposals by non technical people? I'll be happy to geo
put it together.

Christian

Sent from my mobile phone.  Please excuse any touchscreen-induced weirdness.
On May 9, 2014 11:00 AM, "Philip Jägenstedt" <philipj@opera.com> wrote:

> As far as I am concerned, the plan to take WebVTT to Recommendation
> status in the TTWG has no impact at all, it will be a mere snapshot.
> For as long as I am one of the editors, I will continue to look at
> feedback and adjust the spec accordingly. This is how most Web
> specifications work these days, including HTML, DOM and others.
>
> In other words, there is no need to rush. (There's no guarantee that
> stuff in the spec will be implemented anytime soon, anyway.)
>
> Philip
>
> On Fri, May 9, 2014 at 4:46 PM, Christian Vogler
> <christian.vogler@gallaudet.edu> wrote:
> > How much time do we have to do this work, given the timeline of the W3C
> > processes?  I have been talking to consumer advocates in the US and there
> > are some complicated issues about readability and rendering expectations
> > that will take us time to work through and verify that WebVTT meets them.
> > Some specific edge cases also might be more important than some
> previously
> > thought.
> >
> > The best thing to resolve these issues would be to have easily accessible
> > visual renderings of how the different proposals affect the referring of
> > text in various use cases. I presume there are some scattered here and
> there
> > across the bug tracker, but having or working on something consolidated
> that
> > I can point folks who consume captions for a living at, and tell them to
> let
> > us know what they think would be hugely helpful.
> >
> > I'm going to have to follow up again due to lack of time right now, but
> I'm
> > also concerned about the metadata aspects of the proposed changes.
> >
> > More later.
> >
> > Christian
> >
> > Sent from my mobile phone.  Please excuse any touchscreen-induced
> weirdness.
> >
> > On May 9, 2014 10:33 AM, "Philip Jägenstedt" <philipj@opera.com> wrote:
> >>
> >> On Wed, May 7, 2014 at 11:45 AM, Nigel Megitt <nigel.megitt@bbc.co.uk>
> >> wrote:
> >>
> >> > So what are the model features that may need to be brought into
> WebVTT?
> >> > In
> >> > no particular order:
> >> > 1. Independent timing of regions, e.g. so that they can be painted
> even
> >> > when they don't contain text.
> >> > 2. Ability to select for styling purposes regions including setting
> >> > background and line painting colors, padding and zIndex (to define
> >> > painting order if multiple regions overlap). The ::cue-region
> >> > pseudo-element appears to partially fulfil this already.
> >> > 3. Ability to select for styling purposes text contained within a
> >> > particular region.
> >> > 4. Ability to assign metadata additional to identifiers for regions.
> >> > (need
> >> > use cases for this in a WebVTT context)
> >>
> >> My current focus is on simplifying regions as much as possible.
> >> However, if you have strong use cases for any of these additions,
> >> please do file new bugs. Example videos or video frames to illustrate
> >> would be much appreciated.
> >>
> >> Philip
> >>
> >
>