Skip to content
Permalink
Browse files

[e] (0) elaborate on the note-to-self about video activation behaviour

git-svn-id: http://svn.whatwg.org/webapps@3525 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Aug 2, 2009
1 parent 86b88a6 commit 0122ef276e99d528f01d00ba11e411da48787c07
Showing with 26 additions and 4 deletions.
  1. +13 −2 index
  2. +13 −2 source
15 index
is available; otherwise it is 150 CSS pixels.</p>

<hr><!-- XXX (awaiting more impl experience)
default activation behavior is to do the play() if paused, pause()
otherwise
Make the default activation behavior be to do the play() if paused,
pause() otherwise?
The implementation experience that I am awaiting is basically, does
the above make sense? It would mean that the author could bind an
access key to the play/pause behaviour, but is that really useful,
when the author can just script the whole control if desired? It
would mean that if the author called .click() on the element, it
would play/pause the element, as well as firing an event. It would
also mean that while every other control could be controlled by the
user agent (when controls="" is set) and the author (via script),
clicking anywhere on the video, whether the element had a
controls="" attribute or not, would always play/pause the video.
It would also prevent putting a <video> in a link.
--><p>User agents should provide controls to enable or disable the
display of closed captions associated with the video stream, though
such features should, again, not interfere with the page's normal
15 source
<hr>

<!-- XXX (awaiting more impl experience)
default activation behavior is to do the play() if paused, pause()
otherwise
Make the default activation behavior be to do the play() if paused,
pause() otherwise?
The implementation experience that I am awaiting is basically, does
the above make sense? It would mean that the author could bind an
access key to the play/pause behaviour, but is that really useful,
when the author can just script the whole control if desired? It
would mean that if the author called .click() on the element, it
would play/pause the element, as well as firing an event. It would
also mean that while every other control could be controlled by the
user agent (when controls="" is set) and the author (via script),
clicking anywhere on the video, whether the element had a
controls="" attribute or not, would always play/pause the video.
It would also prevent putting a <video> in a link.
-->

<p>User agents should provide controls to enable or disable the

0 comments on commit 0122ef2

Please sign in to comment.
You can’t perform that action at this time.