522339 - Create Toolkit :: Video/Audio Controls component

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Justin Dolske [:Dolske]]

We currently have Core :: Video/Audio, which isn't really the right place for the front-end controls, it's more about the back-end implementation of media support. Now that the backend development has stabilized, video control bugs are less likely to be closely tied to core issues, and it feels like they're shoehorned into the wrong place.

There's Toolkit :: XUL Widgets, which could be used, but that doesn't seem like the right spot either. The video/audio controls happen to be XUL, but users are not going to find that component, and I'd expect that the people interested in watching for media control bugs are not going to want to watch the whole of XUL Widgets.

So, makes sense to me to create a separate component. Roc was ok with the idea too.


New component name: Toolkit :: Video/Audio Controls

Description: For problems related to the default controls used in HTML 5 media elements (<video> and <audio>).

QA Contact: [e-mail]

Default assignee: nobody

Comment 1

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #0)
> and it feels like they're shoehorned into the wrong place.

Is it a nuisance in practice to have them grouped together? I think that Core::Video/Audio is a fine place for them conceptually. I think we should probably even consider moving the code out of the toolkit hierarchy so that they're closer to the relevant gecko code, but maybe there's context about that decision that I'm missing.

Comment 2

[timeless]

the group of people working on the front end and the group of people working on the back end are likely to be distinct.

Comment 3

[:Gavin Sharp [email: [e-mail]]]

dolske should correct me if I'm wrong, but I don't think that applies in this case (at least not so much that the people working on frontend bugs couldn't deal with getting mail for backend changes, or vice-versa).

Comment 4

[Justin Dolske [:Dolske]]

Ok, talked with Gavin on IRC and this should be good to go now. Timeless's point in comment 2 is also what I was thinking; the UX folks and I are less interested in the core pieces, but want to watch front end development.

Comment 5

[Marcia Knous [:marcia]]

Resolving fixed as this has been created.