Re: Implementation Status [via Web Media Text Tracks Community Group]

Agreed. If somebody would like to make that test suite more complete and
host the results in a nice visual manner at webvtt.org, I'd be quite happy
to make Webvtt.org available for that. I wasn't it to be used for something
useful to the community.

Best Regards,
Silvia.
On 26 Feb 2015 14:41, "Philip Jägenstedt" <philipj@opera.com> wrote:

> https://github.com/w3c/web-platform-tests/tree/master/webvtt is the
> best vendor-neutral test suite we have for WebVTT. It's not entirely
> up to date, but has seen some maintenance, so please take a look and
> send pull requests if you find problems :)
>
> Philip
>
> On Thu, Feb 26, 2015 at 6:52 AM, Frank Olivier
> <Frank.Olivier@microsoft.com> wrote:
> > Wrt the required header - I'll get that fixed up in our engine ASAP.
> >
> > I'd love to see the test suite, if there is one...
> >
> > Thanks
> > Frank
> >
> > -----Original Message-----
> > From: Simon Pieters [mailto:simonp@opera.com]
> > Sent: Tuesday, February 24, 2015 1:06 AM
> > To: public-texttracks@w3.org; Silvia Pfeiffer
> > Subject: Re: Implementation Status [via Web Media Text Tracks Community
> Group]
> >
> > On Sun, 22 Feb 2015 07:42:27 +0100, W3C Community Development Team <
> team-community-process@w3.org> wrote:
> >
> >> I recently did a comparison of the implementation status of WebVTT
> >> features in the major browsers.
> >> You can find it here: http://www.webvtt.org/
> >
> > Nice. I'm a bit surprised IE implements the old "WEBVTT FILE" header.
> >
> > Could you also test Opera 12 (Presto)? From memory, I think its support
> is something like:
> >
> > Required Header WEBVTT
> > File MIME Type  sniffing
> > Menu in video controls to select tracks
> > JavaScript TextTrack API        ✔
> > Rendering of text-only captions & subtitles     ✔
> > Cue styling with ::cue and ::cue()      ✔
> > Cue markup incl. Timestamps     ✔ (<ruby> is rendered inline)
> > Vertical Cue setting
> > Line, Align, Position, Size Cue settings        ✔
> > Comments (NOTE) ✔
> > Regions
> > Rendering of text descriptions
> > Rendering of chapters
> >
> > It's not clear to me what it means for an implementation to support
> "Comments (NOTE)" since it falls out of the parsing requirements to discard
> them even before NOTE was in the spec.
> >
> > How do you determine if a feature is "✔" or "✔ (buggy)" or ""? Are you
> running a testsuite?
> >
> > --
> > Simon Pieters
> > Opera Software
> >
>