On Thu, 5 Apr 2007, L. David Baron wrote:
So why not give 'media-loop-start-time' an initial value (traditionally
called 'auto') that makes it use the value from 'media-start-time',
rather than forcing the author to specify the same thing twice for the
normal case? (And likewise for
On Wed, 21 Mar 2007, Robert Brodrecht wrote (in response to Apple's
proposal, quoted):
If the presentation of timed media by the user agent has been disabled, if
the resource has an unsupported type, or if the preparations for its
presentation fail either because of a protocol failure or
On Wed, 21 Mar 2007, Robert Sayre wrote:
My two cents: we should put off events and other API pieces that address
editing applications. It is possible to write web versions of things
like iMovie and SoundEdit in Flash right now, but I don't think it is
realistic to capture that stuff in a
On Thu, 22 Mar 2007, Sander Tekelenburg wrote:
http://webkit.org/specs/HTML_Timed_Media_Elements.html
I'm worried about The controller attribute is a boolean attribute. If
the attribute is present, the user agent must display a user interface
which allows the user to control the media
On Thu, 22 Mar 2007, Dave Raggett wrote:
From an accessibility perspective the proposal lacks support for
captioning. There should be a mechanism for enabling/disabling captions
to avoid disadvantaging people who have difficulties with hearing the
audio. It should further be possible to
On Thu, 22 Mar 2007, Nicholas Shanks wrote:
Volume has the range 0-100 in the DOM interface, but 0.0-1.0 in CSS. These
should be consistent (I favour zero to one and allowing percentages).
The spec now uses a float and 0.0 .. 1.0.
I think that the ERROR state attribute should have a value
At 0:30 + 13/10/07, Ian Hickson wrote:
On Thu, 22 Mar 2007, Dave Raggett wrote:
From an accessibility perspective the proposal lacks support for
captioning. There should be a mechanism for enabling/disabling captions
to avoid disadvantaging people who have difficulties with hearing the
,
David
- Original Message -
From: Maciej Stachowiak [EMAIL PROTECTED]
To: Vladimir Vukicevic [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, April 04, 2007 10:58 PM
Subject: Re: [whatwg] Apple Proposal for Timed Media Elements
On Apr 4, 2007, at 7:31 PM, Vladimir Vukicevic
On Apr 5, 2007, at 4:53 AM, ddailey wrote:
I understand that some here have reasons not to be happy with SMIL,
but its implementation within SVG really is quite nice and
understandable. So far as I can see, the discontent with it stems
primarily from the fact SMIL seems to have
Okay -- I guess that makes sense. thanks.
David
- Original Message -
From: Maciej Stachowiak [EMAIL PROTECTED]
To: ddailey [EMAIL PROTECTED]
Cc: Vladimir Vukicevic [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, April 05, 2007 12:57 PM
Subject: Re: [whatwg] Apple Proposal
Maciej Stachowiak wrote:
On Apr 4, 2007, at 7:31 PM, Vladimir Vukicevic wrote:
1. 'media-loop-count' is an awkward name, especially with The default
value of 1 means the item will play through once but will not loop.
We went through this with APNG, and ended up renaming that member. I
On 4/5/07, Vladimir Vukicevic [EMAIL PROTECTED] wrote:
Maciej Stachowiak wrote:
On Apr 4, 2007, at 7:31 PM, Vladimir Vukicevic wrote:
1. 'media-loop-count' is an awkward name, especially with The default
value of 1 means the item will play through once but will not loop.
We went through
To: [EMAIL PROTECTED]
Subject: Re: [whatwg] Apple Proposal for Timed Media Elements
On 4/5/07, Vladimir Vukicevic [EMAIL PROTECTED] wrote:
Maciej Stachowiak wrote:
On Apr 4, 2007, at 7:31 PM, Vladimir Vukicevic wrote:
1. 'media-loop-count' is an awkward name, especially with The default
value
, April 05, 2007 8:27 PM
To: [EMAIL PROTECTED] List
Subject: Re: [whatwg] Apple Proposal for Timed Media Elements
That said, I wonder whether it would be cleaner to put all (or a
bunch) of these in a single property with a complicated value syntax
rather than splitting it across a whole bunch
Maciej Stachowiak wrote:
CSS Timed Media Module proposal - http://webkit.org/specs/
Timed_Media_CSS.html
Some feedback on my initial reading.. the CSS properties specified seem
like a good set that will cover most common functionality. Some
comments about the spec, though:
1.
On Apr 4, 2007, at 7:31 PM, Vladimir Vukicevic wrote:
Maciej Stachowiak wrote:
CSS Timed Media Module proposal - http://webkit.org/specs/
Timed_Media_CSS.html
Some feedback on my initial reading.. the CSS properties specified
seem like a good set that will cover most common
On 3/21/07, Chris Double [EMAIL PROTECTED] wrote:
Looping is useful for more presentational uses of video. Start and
end time are useful in case you want to package a bunch of small bits
of video in one file and just play different segments, similar to the
way content authors sometimes have
Maciej Stachowiak wrote:
I think audio can use almost the exact same APIs for most things as
video. This has the nice side benefit that new Audio() can just make
an audio element and provide all the relevant useful API.
To me, the distinction between the audio element and the Audio object
On Mar 22, 2007, at 2:09 AM, Dave Raggett wrote:
From an accessibility perspective the proposal lacks support for
captioning. There should be a mechanism for enabling/disabling
captions to avoid disadvantaging people who have difficulties with
hearing the audio. It should further be
On Thu, 22 Mar 2007 01:08:26 +0100, Maciej Stachowiak [EMAIL PROTECTED]
wrote:
- We have included a mechanism for static fallback based on container
type and codec, so that it's possible to choose the best video format
for a client even if user agent codec support varies.
The covered
Ian Hickson wrote:
Biting off more
than we can chew is a common mistake in Web specification development.
lynx -dump -nolist http://www.whatwg.org/specs/web-apps/current-work/ |
wc --words
143147
lynx -dump -nolist http://www.whatwg.org/specs/web-forms/current-work/ |
wc --words
40523
If 21.3 can be handled - get big_264.mp4
else
if 20.9 can be handled - get medium.mp4
else
get small.png
additionally get small2.png
or to put it another way
What if I can't do 21.3, but can do 20.9, do I show the 21.3.
fallback or not?
You show
On 22 Mar 2007, at 00:08, Maciej Stachowiak proposed:
CSS Timed Media Module
HTML Timed Media Elements
• On volume:
The volume property is currently inconsistent in the string names
defined:
http://webkit.org/specs/Timed_Media_CSS.html#propdef-volume
Value: reads silent | soft | medium |
Hello WHAT Working Group,
With the recent discussions about the video element, we've decided
to post our own proposal in this area. This proposal is a joint
effort from the Safari/WebKit team and some of Apple's top timed
media experts, who have experience with QuickTime and other media
On Mar 21, 2007, at 7:20 PM, Robert Brodrecht wrote:
On Mar 21, 2007, at 5:08 PM, Maciej Stachowiak wrote:
The DOM attribute currentRate is the rate at which a media element
is currently playing.
I'm guessing this would be in frames per second? Is it the frames
per second it is
25 matches
Mail list logo
