Currently the controls used for <audio> and <video> are basically exactly the same, with just some minimal changes to avoid -- usually -- showing the content area for <audio> (since it has no visual component). The goal for this meta bug is to collect the dependencies needed to be able to confidently say that <audio> is a first-class citizen with minimal quirky behavior.

Bug 694664 is to remove the volume slider, thus treating video and audio equally. If that bug is fixed then this bug can be closed.

Hi, Dolske I was trying to figure out how event handling be implemented in de-xul version, however it seems need a further arrangement to work out. And I think this bug might be a good step to start with at this stage, but not sure is doable now. Since there's plenty of logic overlapped with video, I expect the result be like adding a new binding named as "audioControls" ,inherited from video control and disable all video related stuff. I didn't get too much context about this initiative, could you give me a advice whether this is a correct direction to go? Thanks:)

This is a pretty generic bug, so it's hard to give any concrete advice because it's not clear what the exact goals are. (So, really, step 1 is defining what we want controls optimized for <audio> to be/do.) I think the intent when I added this to the bug 1271768 cluster was that someone should would with UX to do that defining. (We could also just take this out of the cluster if it doesn't make sense to do that right now.)