The browser could control this, yes; however I believe that the browser should really be as transparent as possible <br>as to not be a limiting factor in development.<br><br>there can always be browser defaults that take over, but by allowing authors the ability to override the browsers controls
<br>will allow for the flexibility of <br>a) allowing for disabled controls (perhaps disabling fast-forward for training videos)<br>b) scripted controls (automatically pausing at various points )<br>c) it allows for cross-browser standardization.
<br><br><br><div><span class="gmail_quote">On 3/25/07, <b class="gmail_sendername">Elliotte Harold</b> <<a href="mailto:elharo@metalab.unc.edu">elharo@metalab.unc.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Chris Adams wrote:<br>> Actually that sounds like a splendid idea to me.<br>> although I am not sure about using the form tag. what about something like?<br>><br>> <video src='some_file.ogg'><br>
> <button type='rewind' /><br>> <button type='playpause' /><br>> <button type='stop' /><br>> <button type='fastforward' /><br>> </video><br>
><br><br>Why should the page be specifying the controls? Shouldn't this be up to<br>the browser?<br><br>--<br>Elliotte Rusty Harold <a href="mailto:elharo@metalab.unc.edu">elharo@metalab.unc.edu</a><br>Java I/O 2nd Edition Just Published!
<br><a href="http://www.cafeaulait.org/books/javaio2/">http://www.cafeaulait.org/books/javaio2/</a><br><a href="http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/">http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/
</a><br></blockquote></div><br><br clear="all"><br>-- <br><a href="mailto:Chris@tuesdaybegins.com">Chris@tuesdaybegins.com</a><br><a href="http://www.tuesdaybegins.com">http://www.tuesdaybegins.com</a>