Re: [csswg-drafts] [scroll-animations-1] [web-animations-2] Clarifying behavior of getCurrentTime(rangeName) (#8114)

The CSS Working Group just discussed `[scroll-animations-1] [web-animations-2] Clarifying behavior of getCurrentTime(rangeName)`, and agreed to the following:

* ``RESOLVED: `getCurrentTime` should just match the internal calculation for the time value which is unclamped``

<details><summary>The full IRC log of that discussion</summary>
&lt;argyle> flackr: the behavior of get current time<br>
&lt;argyle> flackr: the behavior of `getCurrentTime`<br>
&lt;argyle> flackr: kevin want to introducer the issue?<br>
&lt;argyle> flackr: kevin raised the issue that in the spec getCurrentTime produced values between 0 and 100%, but it does produce times outside of it<br>
&lt;argyle> flackr: proposal is `getCurrentTime` should just match the internal calculation for the time value<br>
&lt;argyle> kevin: we're talking about removing the clamping<br>
&lt;argyle> flackr: we already resolved in a different issue that the current time is not clamped, this updates the spec to be consistent with that<br>
&lt;argyle> fantasai: and then it seems like if that range is 0, and if youre' outside of it you return infinity<br>
&lt;argyle> flackr: if you used getCurrentTime and then set this time on anoather animation, returning plus or minus infinity would give you the same effect that that timeline wouuld produce, because you're forcing it into it's before or after phase. so i thought it'd be a good thing to do<br>
&lt;argyle> fantasai: so we have to return something, and plus or minus infinity for a 0 range is the only reasonable option<br>
&lt;argyle> flackr: yeah, just to sayyou're before or after that range<br>
&lt;argyle> astearns: alright, any concerns or comments on this proposal?<br>
&lt;argyle> RESOLVED: `getCurrentTime` should just match the internal calculation for the time value which is unclamped<br>
</details>


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


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

Received on Wednesday, 1 February 2023 17:59:56 UTC