On Thu, 01 Mar 2007 19:18:08 +0100, Spartanicus
<[EMAIL PROTECTED]> wrote:
[...] As soon as enough data is received the user agent should start
decoding the video. This means that play() and other methods can
already be used before the resource is downloaded completely.
I strongly dislike audio and/or video that automatically downloads and
starts playing automatically, so much so that I've disabled media player
plugins altogether.
In case you misunderstood what I wrote: It will not start playing
automatically.
Issue: height / width
Currently an issue with supplying height and width for video content
embedded with the object element is that the supplied width and height
includes the chrome and UI controls of the embedded player. That creates
problems for authors who often don't know the size of those elements in
advance, it may depend on the player and/or player skin they use.
Scaling video can be very GPU intensive, so it would be helpful if there
was a way to ensure that video can play in it's native size, whilst at
the same time knowing in advance what room to reserve in the flow for
the media and any player chrome.
The idea is that support for the formats would be native (much like with
<img>) so you wouldn't have a chrome and a player and such...
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
