- From: L. David Baron <dbaron@dbaron.org>
- Date: Thu, 5 Apr 2007 11:26:51 -0700
On Wednesday 2007-04-04 19:58 -0700, Maciej Stachowiak wrote:
> I think the language might have ended up actually defining it wrong.
> The intent of 'media-loop-end-time' is that this is the point where
> you end where repeating, but on the last iteration you go all the way
> to 'media-end-time'. So if 'media-loop-count' has a value of 3, the
> three repetitions would go as follows:
>
> media-start-time ===> media-
> loop-end-time
> media-loop-start-time ===> media-
> loop-end-time
> media-loop-start-
> time ===> media-end-time
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
media-loop-end-time and media-end-time.)
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 of properties.
Generally one of the main considerations in determining what should
be separate properties is what should cascade separately or together
(e.g., what the atomic units of what a user would want to override
are). The only use case I've thought of so far for property
separation here is the ability to force infinite looping, although I
tend to think that would be handled even better by a UA mechanism
that allows the user to force the media to restart (and go through
their specified looping again).
-David
--
L. David Baron <URL: http://dbaron.org/ >
Technical Lead, Layout & CSS, Mozilla Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20070405/2538af86/attachment.pgp>
Received on Thursday, 5 April 2007 11:26:51 UTC