- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Dec 2022 00:57:27 +0000
- To: public-css-archive@w3.org
> `getCurrentTime` is essentially a replacement for `.currentTime` that returns the same concept, but has more expressivity: So I think it makes sense to keep the same name. I don't think we shouldn't do that. We'll confuse authors unnecessarily. We can't deprecate `currentTime` and for the overwhelming majority of use cases it's the right choice. We should be encouraging users to continue using `currentTime` for the sake of compatibility. For users that need a time for a range, there's `getCurrentTimeForRange` for which the function name spells out what the string argument represents. (If we really must use `getCurrentTime` then it needs to take a property bag, not a string.) -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8201#issuecomment-1350193770 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 December 2022 00:57:29 UTC