- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Feb 2022 20:31:48 +0000
- To: public-css-archive@w3.org
Here are my arguments for pixel-based. * The closest analog to what time-based timelines do is to make it represent an absolute length, since they represent absolute time. * Calculating percentage progress from the absolute offset is easy (and vice versa), but going the other way around makes the API feel like it provides the less fundamental bit of information. * Having the value of .currentTime changing as layout expands the content of the scroller, even though the scroll position (i.e. the current time in absolute terms) is not changing, feels odd. * For ViewTimelines, using percentage progress also means that the startTime/endTime values are shifting in indirect and nonlinear ways as the amount of scroller content changes, even if the element does not move or change, which also feels uncomfortable. (The arguments for percentage-based were around mapping animations from one context to another; I unfortunately can't remember exactly what the use case was.) -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7045#issuecomment-1039527712 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 February 2022 20:31:49 UTC