W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2018

Re: [csswg-drafts] [web-animations-1] Replace AnimationEffectTiming(ReadOnly) with setTiming() ?

From: Antoine Quint via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 Jan 2018 08:32:05 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-358232955-1516177924-sysbot+gh@w3.org>
@birtles The way I thought it differed was that you could pass an imcomplete set of properties and not have to start from the output of getTiming() first.

As for the name, `setTiming()` still sounds to me like we're replacing all properties, while `updateTiming()` indicates select properties can be set. Maybe `setTimingProperties()` or `updateTimingProperties()` would be clearer. I don't really give much weight to how React might or might not do something, JS frameworks come and go, Web APIs are forever (for better or worse). But I wouldn't oppose `setTiming()` vs. `updateTiming()`, I think both can work.

@flackr I don't think there is a clear enough difference just by looking at names between `.timing`, `getTiming()` and `getComputedTiming()`.

GitHub Notification of comment by graouts
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2065#issuecomment-358232955 using your GitHub account
Received on Wednesday, 17 January 2018 08:32:46 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:23 UTC