- From: <bugzilla@jessica.w3.org>
- Date: Tue, 13 Sep 2011 20:50:23 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14109
Marat Tanalin (tanalin.com) <mtanalin@yandex.ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtanalin@yandex.ru
--- Comment #4 from Marat Tanalin (tanalin.com) <mtanalin@yandex.ru> 2011-09-13 20:50:22 UTC ---
(In reply to comment #3)
> My point is that your first example of "tuning the service to deliver the best
> experience possible" is actively bad for my use-case, producing a *much worse*
> experience. I'm used to videos buffering fully if I allow them to.
You are free to view videos way you like (videohosting website may have
settings where you can choose buffer usage strategy that is suitable for you
personally). Do not confuse _ability_ to do something with using this always.
What the bug is about is that buffering should be _controllable_ by
web-application _when it's needed_ for a specific case. And this is quite
reasonable. Lack of this feature is one of drawbacks of HTML5 video element
compared with Flash-based players which are much more flexible.
--
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 Tuesday, 13 September 2011 20:50:26 UTC