Re: [csswg-drafts] [scroll-animations-1] currentTime when scroll range is 0? (#7401)

The CSS Working Group just discussed `[scroll-animations-1] currentTime when scroll range is 0?`, and agreed to the following:

* `RESOLVED: In the absence of scroll range, timeline becomes inactive`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> topic: [scroll-animations-1] currentTime when scroll range is 0?<br>
&lt;emilio> github: https://github.com/w3c/csswg-drafts/issues/7401<br>
&lt;emilio> flackr: when you have a scroll timeline the currentTime is effectively the scroll-position / range of scroll<br>
&lt;emilio> ... but if there's no scroll range then you'd have division by zero / infinite range<br>
&lt;emilio> ... we think that the timeline should become inactive when in this state<br>
&lt;emilio> ... rather than being at the beginning or end or something<br>
&lt;emilio> Rossen_: makes sense, question would be: if you have a scrollport that has content which isn't exceeding the scrollable bounds and you resize it, you're saying that only when you have scroll range the timeline is valid<br>
&lt;emilio> ... numerically I get your point<br>
&lt;emilio> ... in the case when the scrollport resizes<br>
&lt;emilio> ... what does that do to the animation?<br>
&lt;emilio> ... you said the timeline becomes invalid?<br>
&lt;emilio> flackr: inactive, which is an existing state, where the currentTime is null<br>
&lt;emilio> ... so basically if you resize so that it's not scrollable the effects will no longer apply<br>
&lt;Rossen_> q?<br>
&lt;emilio> emilio: when you stop applying the effects the animation doesn't pause right? You get discontinuity<br>
&lt;emilio> flackr: that's right, is not weirder than having a very small scroll range<br>
&lt;dholbert> scribenick: dholbert<br>
&lt;emilio> dbaron: can you have overscroll in these elements?<br>
&lt;dholbert> flackr: I don't think so<br>
&lt;emilio> flackr: depends on browser, I think on ~all browsers you don't get overscroll effect<br>
&lt;dholbert> scribenick: emilio<br>
&lt;emilio> ... but on safari desktop it does<br>
&lt;emilio> ... there's also the question of whether the overscroll effect factors in the scroll timeline<br>
&lt;emilio> dbaron: I was just wondering if you could end up with weird effects in the overscroll effect<br>
&lt;emilio> flackr: I think we'd still not have a reasonable range<br>
&lt;Rossen_> ack dbaron<br>
&lt;emilio> ... I think we shouldn't factor the negative range into the effect<br>
&lt;smfr> i agree with not applying overscroll here<br>
&lt;emilio> ... it's more stuff to worry about for developers, plus browsers don't technically limit the amount of stuff you can overscroll<br>
&lt;emilio> dbaron: that's a good enough answer I think<br>
&lt;emilio> RESOLVED: In the absence of scroll range, timeline becomes inactive<br>
</details>


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


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

Received on Wednesday, 20 July 2022 16:33:31 UTC