- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2023 15:53:00 +0000
- To: public-css-archive@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: Pending Brian's potential objections, go with `getCurrentTime(rangeName?)` ``
<details><summary>The full IRC log of that discussion</summary>
<fantasai> s/Topic/Subtopic/<br>
<TabAtkins> flackr: Bikeshedding issue<br>
<TabAtkins> flackr: we added an API to get a range-specific current time<br>
<TabAtkins> flackr: But Brian brought up that when you're not specifying a range, and just getting the time of the timeline, there's already an accessor for that<br>
<TabAtkins> flackr: So q is, should this get a range-specific name, or just consider the .currentTime accessor legacy?<br>
<TabAtkins> flackr: Because one bit about the function is we can return the TypedOM object, rather than just the double that .currentTime returns<br>
<TabAtkins> flackr: I'm slightly in preference to this being the new way to get times, so use a generic name, and have range name specified in options with a property bag as Brian suggested<br>
<TabAtkins> astearns: But Brian thinks we shoudl go with getCurrentTimeForRange()?<br>
<TabAtkins> flackr: Yeah, Brian thinks it's confusing to have another API for something we already have an accessor for<br>
<astearns> ack fantasai<br>
<TabAtkins> flackr: I'm not concerned with calling it getCurrenTtimeForRange(), just need to decide<br>
<TabAtkins> fantasai: My thoughts are we'd add this to get the TypedOM object, and to get it relative to a range.<br>
<TabAtkins> fantasai: Feel like taking a property bag is a little awkward from a usage pov<br>
<TabAtkins> fantasai: I think ranges are a fundamental enough concept that having it just be a string argument is fine<br>
<TabAtkins> flackr: His argument for a property bag is that we dont' want to confused authors, and might want to extend in the future<br>
<TabAtkins> fantasai: Those can go in a property bag<br>
<TabAtkins> astearns: I'm a little concerned with resolving without Brian's okay<br>
<TabAtkins> flackr: Least contentious is to resolve on the ForRange naming, we know Brian is okay with that<br>
<TabAtkins> astearns: fantasai, you okay with ForRange?<br>
<TabAtkins> fantasai: Think it depends on if we want a plain getCurrentTime at any point<br>
<TabAtkins> fantasai: Coujld push to apac call and get Brian on<br>
<fantasai> TabAtkins: I'm mildly against extremely long names, especially if the arg is obvious, extra typing is annoying<br>
<fantasai> TabAtkins: not strongly for/against property bag vs positional argument, but lean towards positional b/c fantasai's arg that it's quite fundamental<br>
<fantasai> TabAtkins: if we put in property bag, we can make an overload later<br>
<fantasai> TabAtkins: for API niceness, I think I like what I believe the spec currently specifies<br>
<fantasai> TabAtkins: getCurrentTime("rangename")<br>
<fantasai> TabAtkins: can add property bag later<br>
<fantasai> flackr: Should we resolve this is what we prefer and ask Brian to take a look?<br>
<TabAtkins> astearns: So proposed reoslution is to use the short name with a string argument, reasons above, ping Brian to see if he wants to object<br>
<TabAtkins> astearns: objections?<br>
<TabAtkins> RESOLVED: Pending Brian's potential objections, go with `getCurrentTime(rangeName?)`<br>
<bramus> 8192?<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-1476492234 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 March 2023 15:53:01 UTC