- From: Ian Hickson <ian@hixie.ch>
- Date: Sun, 19 Jul 2009 11:18:23 +0000 (UTC)
On Mon, 6 Jul 2009, Robert O'Callahan wrote: > > When script creates an audio element using the "new Audio" constructor, > the 'autobuffer' attribute should be automatically set on that element. > Presumably scripts will only create audio elements that they actually > intend to play. Done. On Sun, 5 Jul 2009, Adam Shannon wrote: > > What about slower, public, or WIFI connections that can't support 5 > people going to yahoo.com and having audio of interviews load? Yahoo > would think that everyone would want to listen to at least the first > ~15-30 seconds. On Mon, 6 Jul 2009, Robert O'Callahan wrote: > > What about them? I'm not sure what your point is. > > I think we expect "new Audio" to be used for scripted playing of sounds, > not to create in-page audio elements. On Sun, 5 Jul 2009, Adam Shannon wrote: > > There already low bandwidth would be crippled more than it already is. > (By loading audio files. > > I would love support for in-page audio, it could be used for podcasts, > radio, interviews, ect... On Mon, 6 Jul 2009, Robert O'Callahan wrote: > > For in-page audio, put an <audio> element in the page. Robert is right; inline <audio> handles this fine, and is distinct from new Audio(). -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Sunday, 19 July 2009 04:18:23 UTC