Hi Brian,
On 23/11/2012, at 12:01 AM, Brian Birtles wrote:
>> * At least in its current form, it is overengineered and unusable. An
>> animation API should focus on ease of use, not combining every conceivable
>> animation concept ever invented.
>
> I'd genuinely appreciate your help with reg
(Sorry, the threading is going to be incorrect here. I just joined the list to
follow up this thread.)
Hi,
I wanted to add a few brief comments about the status of Web Animations in
response to some of the concerns raised recently.
Maciej wrote:
> * At least in its current form, it is overeng
I'd also like to object to this as the API is very complicated and doesn't
seem incremental or like it fits with existing platform features.
Also the naming of things is inconsistent and messy. Why are half the
interfaces and properties abbreviated and half of them not?
This doesn't feel baked e
On Nov 8, 2012, at 4:11 PM, Douglas Stockwell wrote:
> I wanted to let you know that work has begun on implementing Web Animations
> in WebKit. New code for this effort will be landed behind the ENABLE_WEB_ANIM
> feature define and a runtime setting. We expect to be turning this define on
> f
I don't think we should support this API in WebKit at this time, because:
* At least in its current form, it is overengineered and unusable. An animation
API should focus on ease of use, not combining every conceivable animation
concept ever invented.
* It hasn't even reached FPWD yet so it's n
Hi webkit-dev!
I wanted to let you know that work has begun on implementing Web Animations
in WebKit. New code for this effort will be landed behind the
ENABLE_WEB_ANIM feature define and a runtime setting. We expect to be
turning this define on for Chromium buildbots so there will be build and
te
6 matches
Mail list logo
