- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 14 Feb 2010 09:35:46 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8731 --- Comment #16 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2010-02-14 09:35:46 --- (In reply to comment #15) > The idea of "autobuffer" is it would do whatever the browser thinks is best. If > we split that into "download everything" and "download minimum needed for > playthrough", then half the sites will use the wrong one (relative to what > people want). If we only have the one option, then the user agent or the user > can decide which to do, which seems to make more sense to me. So, the question really is: who knows best whether the best choice is to buffering "everything" or just "playthrough" - is it the author, the browser or the user? Maybe it is indeed the user. How does the user get the choice? Would the browser vendor that cares about this offer such a difference as a browser preference? Or should "stop buffering" be an option in the video controls? Or the context menu? Is there something we can recommend? > The idea of putting "autoplay" into this attribute is that it doesn't really > make sense to autoplay without autobuffering. The autobuffer attribute is > basically redundant if you want it to autoplay. I still think that autoplay is a different dimension to buffering. It would need to be stated that if autoplay is used, loadhint is automatically set to autobuffer. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 14 February 2010 09:35:48 UTC