On 16 March 2010 15:04, Gregory Maxwell <gmaxwell(a)gmail.com> wrote: .. Nothing is, but transparency is the next cool thing. Agreed. But seems possible to generate streams of video that crash the browser. So.. probably autoplay is evil. (is already evil because is NSFW since distract coworkers ) -- -- ℱin del ℳensaje.

Gregory Maxwell wrote: Would it help adding a <link rel="prefetch"> to the first video in the page? BTW, the current video handling doesn't work without javascript. I thought we provided a link in such case. Now there's just an useless button.

Aryeh Gregor wrote: Yes, there's an info image which leads you to the File: page. Where you also have the useless button. I don't think it's trivial to know that you can download [view in browser] by clicking the filename when you just want to view the video on wikipedia article Foo.

On 3/17/10 1:02 PM, Marco Schuster wrote: Hopefully browsers on phones and low-bandwidth devices could just ignore this attribute. - Trevor

On Wed, Mar 17, 2010 at 4:02 PM, Marco Schuster &lt;marco(a)harddisk.is-a-geek.org&gt; wrote: On Wed, Mar 17, 2010 at 4:40 PM, Marco Schuster &lt;marco(a)harddisk.is-a-geek.org&gt; wrote: The attribute is a hint, which user agents can respect or ignore as they choose. Mobile user agents will probably buffer much more conservatively than desktop UAs -- that's up to them. Other users who don't like auto-buffering might be able to turn it off in their browser options, or switch to a browser that allows them to do that (as with any other feature they want). Or use a browser that doesn't autobuffer at all by default. On top of that, browsers can feel free to autobuffer only the first few seconds, up to the point where they think they can play through the whole video -- not the whole thing. Ten seconds of video now and again is not going to exhaust anyone's bandwidth budget. In real life, the vast majority of people who aren't using cell phones aren't going to use up any bandwidth limit they might have by occasional video downloads, even downloading the whole thing. They would prefer faster video startup via autobuffering (if they're likely to play the video). This is evidenced by the fact that video sites actually do this -- if users were harmed more than helped by autobuffering (or thought they were), popular video sites would avoid it. We should use it for the same reason, wherever we think the user is likely to watch the video -- e.g., on the video page itself. The fact that one can imagine a small minority of users who might hypothetically be harmed by autobuffering does not mean that it's insane.