- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 27 Jan 2010 15:43:30 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8731 --- Comment #10 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2010-01-27 15:43:29 --- (In reply to comment #9) > I also agree that preload="all" should be dropped, for the same reason we > dropped the 'loaded' event: "loaded" is not a useful concept for media files > that may be too large to fit on a client device, or may not be possible to load > fully (eg. a live stream). Separate issue . . . "loaded" just won't do anything in many cases. but preload="all" would mean to preload as much as is reasonable, which might be a lot more than preload="playthrough" in realistic scenarios. E.g., a low-bitrate two-minute video might be loaded fully with no problem if preload="all" is set, but preload="playthrough" might only load the first five seconds. > This is not necessarily true - some engines allow seeking to portions of a > media resource that have not been loaded. But if that part of the resource is not yet buffered, there will be lag when you seek that far. I don't know if this is worth having the extra mode, but it was brought up. -- 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 Wednesday, 27 January 2010 15:43:33 UTC