- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 May 2023 16:37:13 +0000
- To: public-css-archive@w3.org
> Let me know if this requires a separate issue, but I was surprised to see that `getCurrentTime` returns a CSSNumericValue, rather than a [DOMHighResTimestamp](https://w3c.github.io/hr-time/#dom-domhighrestimestamp). I'm guessing that it'd also be worthwhile to hook up its processing/clamping to [current high resolution time](https://w3c.github.io/hr-time/#dfn-current-high-resolution-time) Scroll timelines don't produce millisecond-based times, so we decided that we should future proof APIs with a CSSNumericValue which can represent the difference between milliseconds and percentages. We should still apply the same clamping to those millisecond values in the CSSNumericValue as we do for DOMHighResTimestamp. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8201#issuecomment-1551728665 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 May 2023 16:37:15 UTC