Re: Dropping angle-bracket syntax for animation

Tab Atkins Jr.:
> >
> > Because decorative CSS animation is just a draft currently and content
> > animation with SMIL/SVG is specified and used for years, I think, we can
> > safely assume, that there are only experimental decorative projects
> > outside using CSS animation currently and a huge amount of content using
> > SMIL/SVG.
>
> This is an incorrect assumption.  CSS Transitions and Animations are
> used quite a lot on the web currently, even though they were, until
> recently, only supported in WebKit.  (It helps that Transitions, in
> particular, degrades really well.)
>

This indicates as well, that it is currently only used for experimental
purposes. Concerning WebKit SVG capabilities I found very interesting
issues anyway (tested with different flavours of this program on the
current Debian system) - from no interpretation of SVG at all to problems 
with encoding of XML documents - I think, one of those browsers did not
even display any HTML or plain text. These are fun toys, no browsers ;o) 
This indicates as well, that projects related to WebKit are only experimental,
not intended for normal users ;o)
I'm pretty sure, that some people get this browser run somehow,
with a lot of efforts I can get something out of some of some of these 
browsers as well (simplest one was the generic WebKit browser, but with
a size of some Gigabyte typically nobody will install it), but normal
users will not do this, therefore from my point of view, using this
browser is experimental in general currently ;o) The behaviour for
normal users is not predictable (or it is predictable, that it does not
work without advanced experiments).
For daily use there are for example Opera, Geckos, Konqueror 
(KHTML, KSVG) or Amaya without having so many difficulties 
as with WebKit browsers...

>
> The intention is to broaden the abilities of CSS Transitions and
> Animations based on use-cases, and additionally develop a strong
> Animation API for Javascript that hooks into the same UA machinery and
> lets authors address the more complex functionality (like
> synchronization of separate animations) more easily.

For syncronisation the syncbase values in SMIL/SVG are pretty
simple and straight forward. therefore fortunately no need for
java-script, what has the advantage, that the results are more
predictable and precise for authors ;o)
For me this indicates as well, that CSS animation should align
with SMIL/SVG to improve.
Concerning transitions of course, there are improvements 
required for SMIL/SVG, especially because the only related
feature is currently typically implemented very bad and even
correct implemented not sufficient for all use cases of such a
feature.

Olaf

Received on Wednesday, 3 August 2011 16:36:53 UTC