- From: <bugzilla@jessica.w3.org>
- Date: Fri, 15 Jul 2011 21:19:00 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13276
Tab Atkins Jr. <jackalmage@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jackalmage@gmail.com
--- Comment #1 from Tab Atkins Jr. <jackalmage@gmail.com> 2011-07-15 21:18:59 UTC ---
(In reply to comment #0)
> This may seem like an acceptable alternative, but it requires extra machine
> resources, and playback may not be as smooth, depending on machine resources.
> It's an ugly kludge but it is the only way for an author or editor to have
> complete control over the playback of the video.
It seems acceptable *because* it's not as good. When we can't prevent authors
from doing user-hostile things, making the user-hostile thing worse than the
user-friendly thing is an acceptable fallback. In this case we don't even have
to do anything proactive - the clunkiness just happens for free.
In addition to being hostile to users in general, this seems to be *extra* bad
for users with disabilities, who may need access to the video's playback to
view the content effectively.
(The only case I can imagine where this isn't actively user-hostile is using a
<video> to do some type of animation in a game. It seems perfectly normal to
draw it into the <canvas> then, so the "workaround" is actually just the
standard procedure.)
--
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 Friday, 15 July 2011 21:19:05 UTC