W3C home > Mailing lists > Public > public-html-comments@w3.org > October 2009


From: Arthur Clifford <art@artspad.net>
Date: Thu, 8 Oct 2009 15:46:00 -0700
To: "'Musgrove, Jason L'" <J.L.Musgrove2@wlv.ac.uk>, "'Gervase Markham'" <gerv@gerv.net>, "'Simon Pieters'" <simonp@opera.com>, <public-html-comments@w3.org>
Message-ID: <013401ca4869$1c4c7860$0e14a8c0@iMacPCVirtualMachine>
The clip tag idea is intriguing in that a clip could be audio, video, or an
image. If the clip tag supported optional 'delayBefore' and/or 'delayAfter'
attribute one could conceivably create an animation out of images, including
images of different types. The clips could also have a boolean 'preload'
attribute to indicate whether to load a clip when the video tag is

If the notion of a playlist is supported that would also mean the usual
playlist sorts of functions, next/back/repeat mode/playmode (i.e. shuffle,

-----Original Message-----
From: public-html-comments-request@w3.org
[mailto:public-html-comments-request@w3.org] On Behalf Of Musgrove, Jason L
Sent: Thursday, October 08, 2009 3:25 PM
To: art@artspad.net; Gervase Markham; Simon Pieters;
Subject: RE: Video DOM API

If what is being aimed for is the sequential playing of more than one
media item, why not amend the spec such that the appropriate media
element (either <audio> or <video>) be permitted to have child elements
that define a playlist in lieu of a src attribute (which can still be
used if only one media item is to played), and let the browser take care
of the sequencing without the unnecessary addition of script to do this.

Suggested example:

	<clip src="video1.m4v" />
	<clip src="video2.m4v" />

The API could then be augmented to include a ".clips" property which
represents a collection of the clip elements, and provides appropriate
methods to manipulate the "playlist".
Received on Thursday, 8 October 2009 22:46:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:25 UTC