WebVTT Bug Filing Plan

Overview

Trying to maintain a large patch over a long period of time is painful--the code around it constantly changes and breaks things, it's hard for more than one person to work on it, it's harder to review, etc. A better strategy is to have a group of related, smaller bugs.

We want to break up the track element bug into smaller bugs, and use the current one as a tracking bug. A tracking bug is a bug that lists dependent bugs, and allows people to see when sub-issues get resolved.

We need to file smaller, secondary bugs to deal with the different parts of this work. That way we can (hopefully) land things in batches, and not block the whole thing on being 100% completed. Also, people can work in parallel.

Major Implementation Tasks

Ralph suggested an initial strategy, which I've expanded somewhat:

the nsVideoFrame changes to add the display div. Flowing from this will be other layout considerations, like text positioning, CSS, and other display aspects of the WebVTT spec (not all of which we'll finish this term).

the import and build support for the parser library in media/webvtt. This will include massaging libwebvtt's public API to work well with Mozilla.