Skip to content

Commit c21f741

Browse files
committed
Clarify section on defining image animation in terms of existing css properties
1 parent f744c80 commit c21f741

1 file changed

Lines changed: 13 additions & 6 deletions

File tree

image-animation-property/README.md

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -410,20 +410,27 @@ Properties like `animation-play-state: running | paused`
410410
or `animation-iteration-count: infinite | <number [0,∞]>`
411411
have value space that are similar to what is proposed here.
412412
We could consider treating animated images as CSS animations,
413-
and making (all) existing animation properties apply to them.
413+
and making (all) existing animation properties apply to images with multiple frames,
414+
and attempt to explain the fact that they are animated in terms of CSS properties,
415+
gaining full control over them along the way.
416+
414417
However a “similar“ value space is not an identical value space:
415-
* The `normal` or `controlled` values of `image-animation` are missing from `animation-play-state`, and would not be generally applicable.
418+
* The some values of `image-animation` are image specific
419+
and are missing from `animation-play-state`,
420+
and would not be generally applicable.
416421
* `animation-iteration-count` lacks a value that can default to what the image specifies internally.
417-
* Various other `animation-*` properties lack values that can express what images need. For instance, what about `animation-duration`?
422+
* Various other `animation-*` properties lack values that can express what images need.
423+
For instance, what about `animation-duration`?
418424
* The initial values of the `animation-*` properties are not appropriate for images.
419425

420-
Making the `animation-*` properties be capable of expressing normal image behavior would require significant extensions.
421-
Even if that were done, Unless an additional opt-in is added,
426+
Adding these missing values or smart intial / auto values is certainly possible,
427+
but making the `animation-*` properties be capable of expressing normal image behavior would require significant extensions.
428+
Even if that were done, unless an additional opt-in is added,
422429
this is certain to cause web-compatibility problems,
423430
as `animation-*` properties are widely used on all sorts of elements with decorative or content images,
424431
and so far without any effect.
425432
Turning it on would cause undesired effects in unsuspecting web-sites.
426-
If the regular `animation-*` properties cannot be made to apply by default and would need to be redesigned anyway,
433+
If the regular `animation-*` properties cannot be made to apply by default and would need significant retro-fitting anyway,
427434
it makes little sense to try and shoehorn image animations into them,
428435
even if there are similarities.
429436

0 commit comments

Comments
 (0)