Re: [csswg-drafts] [scroll-animations-1] Animation.getCurrentTime is easily confused with Animation.currentTime (#8201) from CSS Meeting Bot via GitHub on 2023-04-12 (public-css-archive@w3.org from April 2023)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Apr 2023 16:07:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-1505549027-1681315666-sysbot+gh@w3.org>

The CSS Working Group just discussed `[scroll-animations-1] Animation.getCurrentTime is easily confused with Animation.currentTime`, and agreed to the following:

* `RESOLVED: Change getCurrentTime() parameter to a dict to satisfy Brian's/the TAG's concerns.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> astearns: Previously decided on using getCurrentTime() with a position param<br>
&lt;TabAtkins> astearns: Comments since have noted that the tag prefers property bags<br>
&lt;TabAtkins> astearns: And the person who objects to the name would be okay with property bag instead of positional arg<br>
&lt;TabAtkins> astearns: So proposal is to change the previous resolution to use a property bag instead<br>
&lt;TabAtkins> astearns: Comments?<br>
&lt;TabAtkins> `getCurrentTime({ range: "cover" })` looks fine to me<br>
&lt;TabAtkins> astearns: Objections?<br>
&lt;TabAtkins> RESOLVED: Change getCurrentTime() parameter to a dict to satisfy Brian's/the TAG's concerns.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8201#issuecomment-1505549027 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 April 2023 16:07:49 UTC