I wrote the following just now at #120338:

"""
The framework's approach to scrolling assumes that each ScrollPhysics implementation is restartable, or ballistic. The simulation is frequently restarted, and the ScrollPhysics is responsible for not letting that cause problems.

This is a lot like how the framework may frequently rebuild widgets, and if that affects behavior then that's a bug in the widget.

In the case of scrolling, this assumption is very natural because it will automatically be satisfied by any scroll physics so long as it obeys a reasonable ("ballistic") physical metaphor:

• The thing that's scrolling is a physical object in motion.
• Its velocity changes due to physical forces on it, according to Newton's second law.
• Those forces depend only on (a) its current velocity and (b) where it is in its environment.

This metaphor works great for a wide variety of springs, frictional forces, clamping barriers, and other forms of scrolling physics one could dream up. Modulo small bugs (#109675 and #120340), it works great for all of the framework's scroll physics…

… all, that is, except one. The trouble is that one scroll physics, ClampingScrollPhysics, breaks this assumption. [Then that's the issue #120338 is about.]
"""

and added that this assumption doesn't seem to be clearly documented.

As discussed at #120338 (comment) , we might change this assumption in the future, and we've had previous efforts at doing so.

But for now this assumption is very much there. Fundamentally it stems from the fact that ScrollPhysics.createBallisticAnimation takes only (a) a velocity and (b) a ScrollMetrics, where the latter encodes the current position plus some facts like ScrollMetrics.maxScrollExtent that describe the physical environment. In particular, that method isn't provided the old simulation, or any further information from the old simulation like how long it had been running. So removing this assumption will be a significant change, and I think almost certainly a breaking one.

So, even if we eventually remove this assumption, we should first document it.

I plan to write up a PR to make this change. I think the documentation on ScrollMetrics.createBallisticAnimation may be the one place that needs to mention this requirement.