[Bug 10711] <video>: Playlists

https://www.w3.org/Bugs/Public/show_bug.cgi?id=10711

--- Comment #5 from Michael A. Puls II <shadow2531@gmail.com> ---
I think it's important to have the playlist data specified by some element (and
sub elements) like:

<playlist>
    <track>
        <source> for vorbis
        <source> for mp3
    </track>
    <track>
    <track>
        <source> for vorbis
        <source> for mp3
    </track>
    </track>
</playlist>

With xspf for example, you can parse the XML and use the data to create a bunch
of HTML elements to render and interact (via JS events etc.) with the playlist.
But, what would be way more straightforward is to have a playlist element to
specify the data so the browser itself sets up the rendering and interaction of
the element.

For example:

* HTMLPlaylistElement via document.createElement("playlist") and new Playlist()

* HTMLTrackElemenet via document.createElement("track") and new Track();

* <track> will contain one or more <source> elements.

* <track> can contain a few elements for meta data like artist, title etc.

* The playlist object would have prevTrack() and nextTrack() functions and
'load' and 'trackchange" events. removeTrack(range) would be good too.

* A "playlistchanged" event might be good too to save a snapshot of the
playlist for when the user returns to the page.

* A playlist file would be supported too. It'd just be <playlist> as the root
element. It doesn't have to be XML. It could be HTML.

* Some way to associate and load a playlist element from the current document
or external playli8st file into the current media element.

If one wants to set up their own way to render and interact with the playlist,
they can. Just create the playlist element with JS (or import it from the
playlist file) and work with it there instead of appending it to the body or
specifying it via markup.

So, yes, the playlist element should be rendered (width and height styles
honored) by the browser and the browser should do all the setup of interaction
so the playlist looks, feels and works like a foobar/winamp playlist.

The use-case for doing this is to make it way, way easier and less annoying to
deal with playlists.

* Loop, shuffle, random, sorting (different ways, including randomize) and
repositioning of tracks functions should be supported too (or at least have a
way that you can specify a function to call when the use requests one of those)

The xspf format is also kind of overkill, so it's probably best to just make
something simple.

Don't think nesting of playlists is needed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 20 March 2013 12:12:06 UTC