- From: Gavin Carothers <gavin@carothers.name>
- Date: Wed, 23 Dec 2009 17:19:55 -0800
- To: Karl Dubost <karl@la-grange.net>
- Cc: HTMLwg <public-html@w3.org>, comments@daringfireball.net
The corrected text which had already been released by the time I sent this to the list still contains the following: I think the HTML5 spec should be changed such that the value of the autobuffer attribute must be respected. And even if the spec is not changed, web browsers should not choose to ignore it. Web browsers should only buffer HTML5 media content when the autobuffer or autoplay attribute has been explicitly turned on in the markup. --Gavin On Wed, Dec 23, 2009 at 4:55 PM, Karl Dubost <karl@la-grange.net> wrote: > > Le 22 déc. 2009 à 10:47, Gavin Carothers a écrit : >> John Gruber of Daring Fireball on the autobuffer attribute for the >> video element: >> >> http://daringfireball.net/2009/12/html5_video_unusable > > John Gruber stands corrected. > > On Thu, 24 Dec 2009 00:54:34 GMT > In Daring Fireball: Why the HTML5 'Video' Element Is Effectively Unusable, Even in Browsers Which Support It > At http://daringfireball.net/2009/12/html5_video_unusable > > [Update, 22 Dec 2009: In the original version of > this article, I incorrectly reported that Firefox > auto-buffers HTML5 video content by default, as > Safari and Chrome do. It does not, as shown by > Christopher Blizzard’s simple tests here. I regret > the error, and have revised the article > accordingly. For posterity, the source for the > original version is preserved here. You can create > a precise list of changes by doing a diff against > the source for the current
Received on Thursday, 24 December 2009 01:28:05 UTC