W3C home > Mailing lists > Public > public-html@w3.org > September 2012

[Bug 19034] New: Playlist! We need it to <em>easy</em> define.

From: <bugzilla@jessica.w3.org>
Date: Tue, 25 Sep 2012 21:57:16 +0000
To: public-html@w3.org
Message-ID: <bug-19034-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19034

           Summary: Playlist! We need it to <em>easy</em> define.
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#the
                    -source-element
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, shadow2531@gmail.com,
                    silviapfeiffer1@gmail.com


This was was cloned from bug 10711 as part of operation LATER convergence.
Originally filed: 2010-09-24 08:00:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2010-09-24 08:00:18 +0000 
--------------------------------------------------------------------------------
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-source-element

Comment:
Playlist! We need it to <em>easy</em> define.

Posted from: 83.31.38.230
================================================================================
 #1   Silvia Pfeiffer                                 2010-09-24 08:39:27 +0000 
--------------------------------------------------------------------------------
It would be possible to support something like XSPF http://xspf.org/ or
mediaRSS http://www.rssboard.org/media-rss could be supported as input format
to media elements. It's an indirection though.

An alternative is to run your own in JavaScript using the media.load() function
on a list of files.

The biggest question comes when (and if) we want to support standard playlist
functionality in browsers, such as forward to next file/rewind to previous -
then we need additions to the JavaScript API and possibly to the @controls user
controls.
================================================================================
 #2   Ian 'Hixie' Hickson                             2010-09-29 07:10:23 +0000 
--------------------------------------------------------------------------------
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: none yet
Rationale: Playlists are similar to the media element synchronisation problem,
except that instead of having one timeline that is synchronised across multiple
elements, it's handling switching from one to another in real time. I think
we'll probably have some sort of Controller object that gets a list of media
elements and a configuration for how they relate. That's not for this version
though.
================================================================================

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 25 September 2012 21:57:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 25 September 2012 21:57:21 GMT